> ## 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. # Record a donation through Zapier > Records a donation through donations.create and returns the created record with individual/combined payment amount context. This records the supplied payment outcome without initiating a provider charge. Requires donation management and the relevant donor-form/program access; body idempotency_key supports replay. ## OpenAPI ````yaml post /zapier/actions/donations 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: /zapier/actions/donations: post: tags: - Zapier summary: Record a donation through Zapier description: >- Records a donation through donations.create and returns the created record with individual/combined payment amount context. This records the supplied payment outcome without initiating a provider charge. Requires donation management and the relevant donor-form/program access; body idempotency_key supports replay. operationId: df7e5a81688dcef81d3bbf78c63c1b4d requestBody: description: Validated input accepted by this Zapier transport. required: true content: application/json: schema: required: - donor_id - designation - amount properties: donor_id: description: >- Donor who owns the gift or commitment. Validation: required|integer. type: integer example: 12345 designation: description: >- Recipient/designation identifier for the donation. Validation: required|integer. type: integer example: 4711 amount: description: >- Individual gift amount in the supplied currency. Validation: required|numeric|min:0.01. type: number minimum: 0.01 example: 25 currency: description: >- Stored currency value; legacy callers commonly use a currency symbol. Validation: nullable|string|max:10. type: string maxLength: 10 example: $ nullable: true method: description: >- Stored compatibility payment method identifier. Validation: nullable|integer. type: integer example: 1 nullable: true type: description: >- Record type accepted by this operation. Validation: nullable|integer. type: integer example: 1 nullable: true one_time: description: >- Compatibility one-time gift indicator. Validation: nullable|integer. type: integer example: 1 nullable: true result: description: >- Recorded payment result description. Validation: nullable|string|max:500. type: string maxLength: 500 example: Created via Zapier nullable: true transaction_id: description: >- External transaction reference stored with the record. Validation: nullable|string|max:255. type: string maxLength: 255 example: external-payment-001 nullable: true transaction_status: description: >- Recorded settlement status. Validation: nullable|string|max:100. type: string maxLength: 100 example: completed nullable: true notes: description: >- Internal description associated with the recorded gift. Validation: nullable|string. type: string example: Offline gift received. nullable: true json_fields: description: >- Custom-field values keyed by the configured form field names. Validation: nullable|array. type: object nullable: true additionalProperties: {} refunded: description: >- Whether the recorded gift has a refund. Validation: nullable|boolean. type: boolean example: false nullable: true refunded_amount: description: >- Recorded amount already refunded. Validation: nullable|numeric|min:0. type: number minimum: 0 example: 0 nullable: true is_tax_deductible: description: >- Whether the recorded gift is tax deductible. Validation: nullable|boolean. type: boolean example: true nullable: true idempotency_key: description: >- Stable caller key used by the selected mutation to prevent duplicate records. Validation: nullable|string|max:191. type: string maxLength: 191 example: external-record-001 nullable: true type: object responses: '200': description: >- Created, updated or replayed record; this transport unwraps the primitive success envelope. content: application/json: schema: $ref: '#/components/schemas/Donation' '400': description: The selected primitive rejected the operation. content: application/json: schema: $ref: '#/components/schemas/V3PrimitiveResult' '401': description: The API credential is missing or invalid. content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' '403': description: >- Workspace access, primitive scope, feature availability or Gratona permissions do not permit this request. content: application/json: schema: $ref: '#/components/schemas/V3AccessDenied' '404': description: The referenced record does not exist or is inaccessible. content: application/json: schema: $ref: '#/components/schemas/V3PrimitiveResult' '409': description: >- A duplicate, replay, concurrent lifecycle or identity conflict prevented the write. content: application/json: schema: $ref: '#/components/schemas/V3PrimitiveResult' '422': description: The transport or selected primitive rejected input validation. content: application/json: schema: $ref: '#/components/schemas/ZapierValidationFailure' security: - bearerAuth: [] - apiKeyAuth: [] servers: - url: https://api.gratona.com/v3 description: Gratona V3 automation API components: schemas: Donation: title: Donation description: >- An individual donation transaction. Donations may be one-time or part of a recurring `Commitment`. Despite the name, the `designation` column actually stores the recipient `entity_id` (it predates entities and was never renamed). Tax/refund/QuickBooks state lives on the donation row alongside the gateway transaction id. required: - id - client_id - donor_id - amount - currency properties: id: description: Internal donation ID. type: integer format: int64 example: 983221 client_id: description: Owning Gratona client (multi-tenant scope). type: integer format: int64 example: 207 donor_id: description: Donor who gave this donation. type: integer format: int64 example: 12345 designation: description: >- Recipient entity ID — see `Entity` schema. Historical naming: this is NOT an accounting designation, it is the entity / sponsorship target. Null for unrestricted gifts. type: integer format: int64 example: 4711 nullable: true type: description: >- Donation type code (gateway / source family). Internal enum; values include cash, check, credit card, ACH, in-kind, etc. type: integer example: 1 method: description: >- Payment method code: 1=cash, 2=check, 3=Stripe, 6=PayPal, 8=Stripe-Connect, 9=Flutterwave, 10=Flutterwave-standard, 11=QPayPro, 12=ACH-direct-debit, 13=in-kind. See `config/constants.php` for canonical mapping. type: integer example: 3 nullable: true frequency: description: >- Recurrence cadence: 1=every-month, 2=every-3-months, 3=every-6-months, 4=every-year, 5=one-time, 6=bi-weekly, 7=every-2-months. type: integer enum: - 1 - 2 - 3 - 4 - 5 - 6 - 7 - null example: 5 nullable: true one_time: description: >- True for one-off gifts; false when the donation is part of a recurring commitment. type: boolean example: true duration: description: Optional end date for time-bounded recurring donations. type: string format: date example: '2027-01-15' nullable: true amount: description: >- Persisted donation-line allocation, including any donor-covered processing fee. Existing amounts are preserved. type: number format: float example: 51.5 processing_fee: description: >- Total allocated collection cost in processor_fee_currency: Stripe processing fee plus any Connect platform fee. Eligible fee-free cash/check records return zero; unverified fees remain null. type: number format: float example: 2 nullable: true platform_fee: description: >- Connect application fee breakdown already included in processing_fee. Do not subtract it again from net. Display only when positive. type: number format: float example: 0.5 nullable: true amount_excluding_fee: description: >- Net amount after the inclusive processing_fee, in processor_fee_currency. Original Stripe settlement net, or gross for eligible fee-free cash/check records. Stable compatibility key; later refunds are separate. type: number format: float example: 49.5 nullable: true processor_net_amount: description: Same original settlement net as amount_excluding_fee. type: number format: float example: 49.5 nullable: true processor_fee_currency: description: >- Currency of actual fee and net amounts: Stripe settlement currency (which may differ from donation currency), or donation currency for eligible fee-free cash/check records. type: string example: USD nullable: true donor_covered_fee: description: >- Donor's optional added contribution in the original donation currency, separate from actual gateway expense. type: number format: float example: 1.5 nullable: true processing_fee_known: description: >- Whether valid original Stripe settlement evidence or an eligible fee-free cash/check record establishes fee and net amounts. type: boolean example: true actual_charged_amount: description: >- Total amount the gateway captured for the payment. Shared charges repeat this total on each allocation; it is not a per-line fee. type: number format: float example: 103 nullable: true currency: description: ISO 4217 currency code. type: string example: USD in_kind_category: description: Set only when `method` is in-kind (13). type: string enum: - stocks - goods - services - cryptocurrency - other - null example: goods nullable: true result: description: >- Free-form gateway result (e.g. successful, failed, pending). Gateway-specific values are common. type: string example: successful nullable: true transaction_id: description: >- External payment-gateway transaction ID (Stripe charge id, PayPal capture id, etc.). type: string example: ch_3OqXXXXX nullable: true transaction_status: description: External gateway status string. type: string example: succeeded nullable: true refunded: description: True if the donation has been at least partially refunded. type: boolean example: false refunded_amount: description: Amount refunded so far (in `currency`). type: number format: float example: 0 nullable: true refundable: description: >- Whether the gateway integration believes this donation can still be refunded. type: boolean example: true is_tax_deductible: description: Whether the donation is reportable as tax-deductible giving. type: boolean example: true tags: description: Free-form donor / admin tags. type: array items: type: string example: - matching-gift - year-end nullable: true notes: description: Plaintext notes attached to the donation (memo line, admin remarks). type: string example: 'Memo: in honor of John Doe' nullable: true quickbooks_receipt_id: description: QuickBooks receipt id, if synced. type: string example: qbo_5512 nullable: true receipt_sent_at: description: When the donation receipt email was last sent (null if never). type: string format: date-time example: '2026-01-02T08:30:00Z' nullable: true acknowledged_at: description: >- When this gift was acknowledged for stewardship tracking. Null means pending acknowledgement. type: string format: date-time example: '2026-01-03T10:15:00Z' nullable: true acknowledged_by_user_id: description: Admin user who last acknowledged the gift, when known. type: integer format: int64 example: 42 nullable: true acknowledgement_source: description: How the gift was acknowledged. type: string enum: - manual - auto_email - receipt - mailing - interaction - import - null example: manual nullable: true acknowledgement_context_json: description: >- Lightweight acknowledgement metadata such as note, previous state, or receipt context. type: object nullable: true additionalProperties: true json_fields: description: >- Custom profile/record fields. Raw model responses retain the encoded JSON string; projection endpoints may return a decoded map or list. Use the record form definition to interpret field keys. anyOf: - type: string nullable: true - type: object additionalProperties: true - type: array items: {} batch_id: description: Set when imported via CSV; groups donations imported together. type: integer format: int64 example: null nullable: true is_csv_import: description: >- True when the row was created from a CSV import (vs. live gateway charge). type: boolean example: false created_at: type: string format: date-time example: '2026-01-02T08:25:00Z' updated_at: type: string format: date-time example: '2026-01-02T08:30:00Z' deleted_at: type: string format: date-time example: null nullable: true type: object V3PrimitiveResult: description: >- The PrimitiveResult envelope serialized by primitive invocation and validation. required: - success - data - errors - warnings - meta properties: success: description: Whether the selected primitive succeeded. type: boolean example: true data: description: >- Operation-specific JSON result, or null on failure. Its schema is returned by primitive discovery. nullable: true errors: description: Domain errors or validation field errors. type: array items: properties: code: description: Machine-readable error code. type: string example: VALIDATION_ERROR message: description: Domain error explanation when present. type: string example: Record was not found. details: description: Additional domain-specific error details. field: description: Invalid input field for validation errors. type: string example: donor_id messages: description: Validation messages for that field. type: array items: type: string type: object warnings: description: Non-fatal operation warnings. type: array items: type: string meta: description: >- Operation metadata; may contain status, dry_run, replay information or pagination. Empty metadata serializes as an empty array. 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 V3AccessDenied: description: >- Scope/primitive denials or the authentication middleware workspace-access denial. oneOf: - $ref: '#/components/schemas/V3DiscoveryError' - $ref: '#/components/schemas/ErrorResponse' ZapierValidationFailure: description: >- Laravel transport validation map or primitive validation/domain error envelope. oneOf: - $ref: '#/components/schemas/ValidationErrorResponse' - $ref: '#/components/schemas/V3PrimitiveResult' V3DiscoveryError: description: >- V3 discovery errors; primitive failures may additionally include data, warnings and meta. required: - success - errors properties: success: description: False when discovery or authorization fails. type: boolean example: false errors: description: Structured operation errors. type: array items: properties: code: description: Machine-readable failure code. type: string example: INSUFFICIENT_SCOPE message: description: Human-readable explanation. type: string example: Required scope is missing. required_scope: description: Required scope when reported by the guard. type: string example: schema:read available_scopes: description: Credential scopes when reported by the schema guard. type: array items: type: string required_permission_groups: description: Permission alternatives grouped by required access boundary. type: array items: type: array items: type: string type: object 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 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 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.