> ## 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. # Update a donor through Zapier > Updates the supplied safe profile fields through donors.update. Requires donors_manage, donor-form access and the primitive scope. The returned body is the donor record; duplicate email or stewardship household-impact conflicts may prevent the write. ## OpenAPI ````yaml patch /zapier/actions/donors/{id} 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/donors/{id}: patch: tags: - Zapier summary: Update a donor through Zapier description: >- Updates the supplied safe profile fields through donors.update. Requires donors_manage, donor-form access and the primitive scope. The returned body is the donor record; duplicate email or stewardship household-impact conflicts may prevent the write. operationId: 0ac7b4147853af054ded8155685b34c1 parameters: - name: id in: path description: Identifier of the existing record in the authenticated organization. required: true schema: type: integer example: 12345 requestBody: description: Validated input accepted by this Zapier transport. required: false content: application/json: schema: properties: email: description: 'Profile email address. Validation: nullable|email.' type: string format: email example: jane@example.org nullable: true username: description: 'Donor portal username. Validation: nullable|string|max:255.' type: string maxLength: 255 example: jane.doe nullable: true first_name: description: >- Individual donor given name. Validation: nullable|string|max:255. type: string maxLength: 255 example: Jane nullable: true last_name: description: >- Individual donor family name. Validation: nullable|string|max:255. type: string maxLength: 255 example: Doe nullable: true organization_name: description: >- Organization donor display name. Validation: nullable|string|max:255. type: string maxLength: 255 example: Example Foundation nullable: true phone: description: >- Profile telephone number. Validation: nullable|string|max:50. type: string maxLength: 50 example: '+12565550123' nullable: true household_id: description: >- Household membership for the donor. Validation: nullable|integer. type: integer example: 88 nullable: true do_not_email: description: >- Whether the donor has opted out of email. Validation: nullable|boolean. type: boolean example: false nullable: true json_fields: description: >- Custom-field values keyed by the configured form field names. Validation: nullable|array. type: object nullable: true additionalProperties: {} type: object responses: '200': description: >- Created, updated or replayed record; this transport unwraps the primitive success envelope. content: application/json: schema: $ref: '#/components/schemas/Donor' '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: Donor: title: Donor description: >- A donor record. Donors give one-time donations and recurring commitments, and may be linked to entities (recipients) via sponsorships. Standardized profile columns (first_name, phone, address, etc.) coexist with arbitrary custom fields stored in `json_fields` and defined per `hysform_id`. The `username`/`email`/`password` columns also let donors sign in to the donor portal. required: - id - client_id properties: id: description: Internal donor ID. type: integer format: int64 example: 12345 client_id: description: >- Owning Gratona client (multi-tenant scope). All donor queries MUST filter by this. type: integer format: int64 example: 207 hysform_id: description: >- HysForm that defines this donor's profile fields (custom + standardized) — controls which keys appear in `json_fields`. type: integer format: int64 example: 42 nullable: true donorprogram_id: description: >- Program the donor signed up under, if applicable. Mostly informational. type: integer format: int64 example: 11 nullable: true household_id: description: >- Household this donor is linked to, when joint giving / partner records are tracked together. type: integer format: int64 example: 88 nullable: true type: description: >- Canonical donor identity type is INDIVIDUAL or ORGANIZATION. Compatibility serializers/callers may retain the lower-case aliases. type: string enum: - INDIVIDUAL - ORGANIZATION - individual - organization - null example: INDIVIDUAL nullable: true username: description: >- Login username for the donor portal. Must be unique across donors when set. type: string example: janedoe nullable: true email: description: Donor email — used for receipts, statements, and donor-portal login. type: string format: email example: jane@example.com nullable: true organization_name: description: >- For `type=organization` donors. Standardized field; mirrored in `json_fields.organization` for legacy clients. type: string example: Acme Foundation nullable: true first_name: description: Donor first / given name. Standardized field. type: string example: Jane nullable: true last_name: description: Donor last / family name. Standardized field. type: string example: Doe nullable: true preferred_contact_method: description: How the donor prefers to be contacted. type: string enum: - email - phone - sms - mail - null example: email nullable: true phone: description: Phone number as entered by the user (display format). type: string example: (555) 123-4567 nullable: true phone_e164: description: >- Phone normalized to E.164 for SMS/dialing. Populated by the phone normalization pipeline. type: string example: '+15551234567' nullable: true can_receive_sms: description: Whether SMS opt-in is granted for this donor. type: boolean example: true street: description: Street address line 1 (standardized). type: string example: 123 Main St nullable: true address_line2: description: Street address line 2 (apartment, unit, suite). type: string example: Apt 4B nullable: true city: description: City. type: string example: Springfield nullable: true state: description: State / region (free-form display value). type: string example: IL nullable: true zip: description: Postal / ZIP code. type: string example: '62704' nullable: true country: description: Country display name. type: string example: United States nullable: true country_code: description: ISO 3166-1 alpha-2 country code. type: string example: US nullable: true subdivision_code: description: ISO 3166-2 country subdivision code. type: string example: US-IL nullable: 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: {} year_to_date: description: >- Cached YTD giving totals (per year and per program), refreshed by background jobs. type: object nullable: true additionalProperties: true has_artifacts: description: Whether the donor has any uploads/photos attached. type: boolean example: false batch_id: description: >- Set when the donor was created via a CSV import batch; ties together donors imported in the same run. type: integer format: int64 example: null nullable: true created_at: type: string format: date-time example: '2025-03-15T19:42:00Z' updated_at: type: string format: date-time example: '2026-01-02T08:11:00Z' deleted_at: description: >- Soft-delete timestamp; donors with a non-null value are excluded from default queries. 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.