> ## Documentation Index
> Fetch the complete documentation index at: https://api-docs.helpyousponsor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prepare a lost-donor reactivation action

> Only bucket=lost_donors is supported. Enabled action may prepare an audience, install a saved cohort view or create deduplicated reactivation Work, optionally routed to relationship managers. Does not send outreach. Requires permission: donors_view; plus one of donors_manage.



## OpenAPI

````yaml post /admin/fundraising/cohorts/{bucket}/reactivation
openapi: 3.0.0
info:
  title: Gratona API
  description: >-
    REST API for the Gratona fundraising platform, including donor, donation,
    sponsorship, program, event, and integration workflows. Endpoints are
    organized by tag. Most endpoints require either a Passport bearer token or
    an issued API key — see the Security Schemes section.
  contact:
    name: Gratona Engineering
    url: https://gratona.com
    email: devs@gratona.com
  version: 1.0.0
servers:
  - url: https://api.gratona.com/v1
    description: Server Version 1.0.0
security: []
tags:
  - name: Auth
    description: >-
      Login, signup, logout, password reset, and email verification for admin
      users and donors.
  - name: Donors
    description: >-
      Donor records: CRUD, profile fields, household linkage, search, filters,
      merge, and duplicate detection.
  - name: Donations
    description: >-
      Individual donation records, recurring commitments, soft credits, refunds,
      designations, and exports.
  - name: Sponsorships
    description: >-
      Donor-to-entity commitment relationships, lifecycle transitions, and
      commitment-specific filters.
  - name: Entities
    description: >-
      Recipient records (children, families, projects, animals, etc.), their
      status, and entity-level fields.
  - name: Programs
    description: >-
      Program / campaign configuration: hierarchy, settings, and program-level
      metadata.
  - name: Forms
    description: >-
      Custom form builder (HysForm), form fields, standardized donor fields, and
      field migrations.
  - name: Trips
    description: >-
      Mission-trip management: trips, participants, budgets, tasks,
      e-signatures, fundraising milestones, and background checks.
  - name: Communications
    description: >-
      Email templates, SMS, newsletters, donor email manager, and per-donor
      notes.
  - name: Payments
    description: >-
      Payment-gateway management (Stripe, PayPal, Flutterwave, QuickBooks).
      Excludes inbound webhooks — see the Webhooks tag.
  - name: Reports
    description: Dashboards, analytics, scheduled reports, and exports.
  - name: Admin
    description: >-
      Client-account administration: users, groups/permissions, settings,
      integrations, and account lifecycle.
  - name: Donor Portal
    description: >-
      Endpoints consumed by the donor-facing portal (donor login, dashboard,
      donation history, messages).
  - name: Recipient Portal
    description: Endpoints consumed by the recipient-facing portal.
  - name: Public
    description: >-
      Unauthenticated public endpoints: donor signup, public trip pages,
      peer-to-peer campaigns, public checkout.
  - name: Webhooks
    description: >-
      Inbound webhooks from third parties (Stripe, PayPal, Flutterwave, Checkr,
      DropboxSign). Annotated minimally for reference; payload shapes are owned
      by the upstream provider.
  - name: Events
    description: >-
      Event setup, invitations, registration, ticketing, attendance and event
      reporting.
  - name: Journeys
    description: >-
      Journey graphs, activation, enrollment, message templates and event
      follow-up automations.
  - name: Tasks
    description: Workspace tasks, assignments, saved task views and record collaboration.
  - name: Fundraising
    description: >-
      Fundraising portfolios, stewardship plans, giving anniversaries and
      personal donor follow-up.
  - name: Impact Stories
    description: Story intake, review, assets, consent and publication workflows.
  - name: Integrations
    description: Workspace integration connections, mappings, synchronization and recovery.
  - name: Email Calendar
    description: Connected email/calendar accounts and donor interactions.
  - name: Spaces
    description: Workspace Spaces and collaborative Pages.
  - name: Library
    description: Workspace documents, source connections, files and analysis.
  - name: Intelligence
    description: Donor intelligence and Tali workspace workflows.
  - name: Automation
    description: >-
      V3 automation primitive discovery, input validation, invocation and Zapier
      contracts.
  - name: Schema
    description: V3 model, enum, capability and scope discovery.
  - name: Zapier
    description: Zapier automation connections, polling feeds and actions.
  - name: Files
    description: Files
  - name: Client
    description: Client
  - name: Payment Gateways
    description: Payment Gateways
  - name: Email Settings
    description: Email Settings
  - name: Admin Dashboard
    description: Admin Dashboard
  - name: Recipients
    description: Recipients
  - name: Historical Archived Updates
    description: Historical Archived Updates
  - name: Team & access
    description: Team & access
  - name: Settings
    description: Settings
  - name: Notifications
    description: Notifications
  - name: Participation
    description: Participation
  - name: Users
    description: Users
  - name: Wrapped
    description: Wrapped
  - name: Donor SignUp
    description: Donor SignUp
  - name: Frontend
    description: Frontend
  - name: User
    description: User
  - name: Workspace
    description: Workspace
paths:
  /admin/fundraising/cohorts/{bucket}/reactivation:
    post:
      tags:
        - Fundraising
      summary: Prepare a lost-donor reactivation action
      description: >-
        Only bucket=lost_donors is supported. Enabled action may prepare an
        audience, install a saved cohort view or create deduplicated
        reactivation Work, optionally routed to relationship managers. Does not
        send outreach. Requires permission: donors_view; plus one of
        donors_manage.
      operationId: fundraisingHubReactivation
      parameters:
        - name: bucket
          in: path
          description: Cohort bucket key. Only lost_donors permits reactivation.
          required: true
          schema:
            type: string
          example: lost_donors
      requestBody:
        description: Validated request fields for this operation.
        required: false
        content:
          application/json:
            schema:
              properties:
                acknowledgement_work_scope:
                  description: >-
                    Acknowledgement work scope. Validation: nullable; allowed
                    values: active, historical, all.
                  type: string
                  enum:
                    - active
                    - historical
                    - all
                    - null
                  example: active
                  nullable: true
                fundraiser_user_id:
                  description: >-
                    Relationship-manager id, all or unassigned; scoped by donor
                    visibility.
                  type: string
                  maxLength: 64
                  example: all
                  nullable: true
                group_by_household:
                  description: >-
                    Boolean-like query input; true/false and numeric forms are
                    normalized by this workflow.
                  type: boolean
                  example: false
                  nullable: true
                search:
                  description: 'Search. Validation: nullable, string, max:255.'
                  type: string
                  maxLength: 255
                  example: education
                  nullable: true
                date_from:
                  description: 'Date from. Validation: nullable, date.'
                  type: string
                  format: date-time
                  example: '2026-10-20T12:00:00Z'
                  nullable: true
                date_to:
                  description: 'Date to. Validation: nullable, date.'
                  type: string
                  format: date-time
                  example: '2026-10-20T12:00:00Z'
                  nullable: true
                state:
                  description: 'State. Validation: nullable, string, max:64.'
                  type: string
                  maxLength: 64
                  example: State
                  nullable: true
                comparison_mode:
                  description: 'Comparison mode. Validation: nullable, string, max:64.'
                  type: string
                  maxLength: 64
                  example: Comparison Mode
                  nullable: true
                current_start:
                  description: 'Current start. Validation: nullable, date.'
                  type: string
                  format: date-time
                  example: '2026-10-20T12:00:00Z'
                  nullable: true
                current_end:
                  description: 'Current end. Validation: nullable, date.'
                  type: string
                  format: date-time
                  example: '2026-10-20T12:00:00Z'
                  nullable: true
                comparison_start:
                  description: 'Comparison start. Validation: nullable, date.'
                  type: string
                  format: date-time
                  example: '2026-10-20T12:00:00Z'
                  nullable: true
                comparison_end:
                  description: 'Comparison end. Validation: nullable, date.'
                  type: string
                  format: date-time
                  example: '2026-10-20T12:00:00Z'
                  nullable: true
                refresh:
                  description: >-
                    Boolean-like query input; true/false and numeric forms are
                    normalized by this workflow.
                  type: boolean
                  example: false
                  nullable: true
                page:
                  description: 'Page. Validation: nullable, integer, min:1.'
                  type: integer
                  minimum: 1
                  example: 1
                  nullable: true
                per_page:
                  description: 'Per page. Validation: nullable, integer, min:10, max:100.'
                  type: integer
                  maximum: 100
                  minimum: 10
                  example: 10
                  nullable: true
                action:
                  description: 'Action. Validation: nullable, string, max:64.'
                  type: string
                  maxLength: 64
                  example: Action
                  nullable: true
                due_date:
                  description: 'Due date. Validation: nullable, date.'
                  type: string
                  format: date-time
                  example: '2026-10-20T12:00:00Z'
                  nullable: true
                owner_user_id:
                  description: 'Owner user id. Validation: nullable, integer.'
                  type: integer
                  example: 1
                  nullable: true
                audience_name:
                  description: 'Audience name. Validation: nullable, string, max:255.'
                  type: string
                  maxLength: 255
                  example: Audience Name
                  nullable: true
              type: object
      responses:
        '200':
          description: Operation result.
          content:
            application/json:
              schema:
                properties:
                  status:
                    type: string
                    example: success
                  data:
                    $ref: '#/components/schemas/FundraisingHubReactivation'
                type: object
        '401':
          description: Authentication is required.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnauthorizedResponse'
        '403':
          description: >-
            The authenticated user lacks access to this workflow or its related
            records.
        '422':
          description: Reactivation requires the lost_donors bucket and an enabled action.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RequestRejection'
      security:
        - bearerAuth: []
        - apiKeyAuth: []
components:
  schemas:
    FundraisingHubReactivation:
      description: >-
        May return only a prepared audience, install a saved view or create
        deduplicated Work, depending on enabled action; never sends outreach.
      properties:
        created_count:
          description: Count.
          type: integer
          example: 2
          nullable: false
        action:
          description: Serialized value.
          type: string
          example: Example
          nullable: true
        available_actions:
          type: array
          items:
            type: string
        saved_view:
          properties:
            id:
              description: Identifier in the authenticated organization.
              type: integer
              example: 42
              nullable: false
            name:
              description: Serialized value.
              type: string
              example: Example
              nullable: true
            created:
              description: Workflow state.
              type: boolean
              example: true
          type: object
        audience:
          properties:
            source:
              type: string
              example: fundraising_cohort_lost
            bucket:
              type: string
              example: lost_donors
            donor_ids:
              type: array
              items:
                description: Identifier in the authenticated organization.
                type: integer
                example: 42
                nullable: false
            emails:
              type: array
              items:
                type: string
                format: email
            count:
              description: Count.
              type: integer
              example: 2
              nullable: false
          type: object
        cohort:
          properties:
            current_donors:
              properties:
                count:
                  description: Count.
                  type: integer
                  example: 2
                  nullable: false
                amount:
                  description: Amount or percentage.
                  type: number
                  example: 25
                  nullable: false
                donor_ids:
                  type: array
                  items:
                    description: Identifier in the authenticated organization.
                    type: integer
                    example: 42
                    nullable: false
              type: object
            new_donors:
              properties:
                count:
                  description: Count.
                  type: integer
                  example: 2
                  nullable: false
                amount:
                  description: Amount or percentage.
                  type: number
                  example: 25
                  nullable: false
                donor_ids:
                  type: array
                  items:
                    description: Identifier in the authenticated organization.
                    type: integer
                    example: 42
                    nullable: false
              type: object
            lost_donors:
              properties:
                count:
                  description: Count.
                  type: integer
                  example: 2
                  nullable: false
                amount:
                  description: Amount or percentage.
                  type: number
                  example: 25
                  nullable: false
                donor_ids:
                  type: array
                  items:
                    description: Identifier in the authenticated organization.
                    type: integer
                    example: 42
                    nullable: false
              type: object
            upgraded_donors:
              properties:
                count:
                  description: Count.
                  type: integer
                  example: 2
                  nullable: false
                amount:
                  description: Amount or percentage.
                  type: number
                  example: 25
                  nullable: false
                donor_ids:
                  type: array
                  items:
                    description: Identifier in the authenticated organization.
                    type: integer
                    example: 42
                    nullable: false
              type: object
            downgraded_donors:
              properties:
                count:
                  description: Count.
                  type: integer
                  example: 2
                  nullable: false
                amount:
                  description: Amount or percentage.
                  type: number
                  example: 25
                  nullable: false
                donor_ids:
                  type: array
                  items:
                    description: Identifier in the authenticated organization.
                    type: integer
                    example: 42
                    nullable: false
              type: object
            maintained_donors:
              properties:
                count:
                  description: Count.
                  type: integer
                  example: 2
                  nullable: false
                amount:
                  description: Amount or percentage.
                  type: number
                  example: 25
                  nullable: false
                donor_ids:
                  type: array
                  items:
                    description: Identifier in the authenticated organization.
                    type: integer
                    example: 42
                    nullable: false
              type: object
            retained_donors:
              properties:
                count:
                  description: Count.
                  type: integer
                  example: 2
                  nullable: false
                amount:
                  description: Amount or percentage.
                  type: number
                  example: 25
                  nullable: false
                donor_ids:
                  type: array
                  items:
                    description: Identifier in the authenticated organization.
                    type: integer
                    example: 42
                    nullable: false
              type: object
          type: object
      type: object
    UnauthorizedResponse:
      title: UnauthorizedResponse
      description: >-
        Returned with HTTP 401 when the request lacks a valid Passport bearer
        token, a valid `X-HYS-API-Key`, or a valid session. The body is the
        simple `{message, status}` envelope emitted by `AuthenticateApiOrKey`.
      required:
        - message
        - status
      properties:
        message:
          description: >-
            Always the literal string `Unauthorized` from the `auth.api_or_key`
            middleware. Login endpoints return `Invalid Credentials` instead.
          type: string
          example: Unauthorized
        status:
          type: string
          example: error
      type: object
    RequestRejection:
      description: >-
        Request or workflow rejection. Framework field-validation failures
        contain errors; semantic rejections may contain message without errors;
        legacy/provider failures may use error and error_code. The operation
        description identifies the rejected condition. Domain responses may add
        current revision, limits or other conflict context.
      anyOf:
        - $ref: '#/components/schemas/ValidationErrorResponse'
        - $ref: '#/components/schemas/ErrorResponse'
        - required:
            - error
          properties:
            error:
              description: Legacy or provider-facing error message.
              type: string
              example: The request could not be completed.
            error_code:
              description: Stable domain error code, when provided.
              type: string
              example: WORKFLOW_UNAVAILABLE
          type: object
    ValidationErrorResponse:
      title: ValidationErrorResponse
      description: >-
        Returned with HTTP 422 when `Validator::make($data, $rules)` fails. The
        `errors` map is keyed by the failing field name; each value is an array
        of human-readable error messages for that field. Most controllers also
        include a top-level `status: error`.
      required:
        - errors
      properties:
        errors:
          description: >-
            Map of field name to array of validator error messages. Example:
            `{email: [The email field is required.], amount: [The amount must be
            a number.]}`.
          type: object
          additionalProperties:
            type: array
            items:
              type: string
        status:
          description: Always the literal string `error`.
          type: string
          example: error
        message:
          description: >-
            Optional summary message — present on some endpoints, absent on
            others.
          type: string
          example: The given data was invalid.
          nullable: true
      type: object
    ErrorResponse:
      title: ErrorResponse
      description: >-
        Generic error envelope used by most controllers. Most error responses
        pair a human-readable `message` with `status: error`. Some endpoints
        additionally include `errors` (validator errors), `error` (legacy
        single-error string), `code`, or domain-specific context fields.
      required:
        - message
      properties:
        message:
          description: Human-readable error message.
          type: string
          example: Something went wrong. Please try again.
        status:
          description: >-
            Always the literal string `error` for failures. Some endpoints omit
            this field.
          type: string
          example: error
        error:
          description: Legacy single error code/string used by older endpoints.
          type: string
          example: invalid_request
          nullable: true
        code:
          description: >-
            Optional application-level error code (not all endpoints populate
            this).
          type: string
          example: DONOR_NOT_FOUND
          nullable: true
      type: object
  securitySchemes:
    bearerAuth:
      type: http
      description: Passport bearer token authentication for legacy admin sessions.
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      description: Gratona API key sent with the compatibility header X-HYS-API-Key.
      name: X-HYS-API-Key
      in: header

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.