> ## 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. # Resolve a reviewed donor identity collision > Defaults to match_separate_donor. Uses the expected run/current-donor/claim guards under lock; competing reviews and newer evidence are rejected. Matching writes the source identity mapping and can move an existing claimed mapping only to an explicitly selected separate donor. source_record_merged resolves local evidence; a missing-source decision retires its obsolete mapping and clears only matching legacy source-id fields. Donor records are not merged and gifts/payments/contact details are preserved. Verify returned source identities before resuming sync. Requires the integration platform global/configured client feature gate (normally integration_platform_foundation). Requires permission: one of access_account_settings. ## OpenAPI ````yaml post /integrations/hub/connections/{connection_id}/donor-identity-decisions/{event_id}/resolve 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: /integrations/hub/connections/{connection_id}/donor-identity-decisions/{event_id}/resolve: post: tags: - Integrations summary: Resolve a reviewed donor identity collision description: >- Defaults to match_separate_donor. Uses the expected run/current-donor/claim guards under lock; competing reviews and newer evidence are rejected. Matching writes the source identity mapping and can move an existing claimed mapping only to an explicitly selected separate donor. source_record_merged resolves local evidence; a missing-source decision retires its obsolete mapping and clears only matching legacy source-id fields. Donor records are not merged and gifts/payments/contact details are preserved. Verify returned source identities before resuming sync. Requires the integration platform global/configured client feature gate (normally integration_platform_foundation). Requires permission: one of access_account_settings. operationId: integrationHubResolveDonorIdentityDecision parameters: - name: connection_id in: path description: Connection id in the current organization. required: true schema: type: integer example: 42 - name: event_id in: path description: Event id in the current organization. required: true schema: type: integer example: 42 requestBody: description: Validated request fields for this operation. required: true content: application/json: schema: required: - expected_sync_run_id properties: decision: description: >- Decision. Validation: sometimes; allowed values: match_separate_donor, source_record_merged. type: string enum: - match_separate_donor - source_record_merged example: match_separate_donor target_hys_donor_id: description: >- Target hys donor id. Validation: required_unless:decision,source_record_merged, integer, min:1. Required unless decision is source_record_merged. type: integer minimum: 1 example: 1 displaced_hys_donor_id: description: >- Displaced hys donor id. Validation: nullable, integer, min:1. Required by the service when the selected target has an existing different source claim. type: integer minimum: 1 example: 1 nullable: true expected_sync_run_id: description: 'Expected sync run id. Validation: required, integer, min:1.' type: integer minimum: 1 example: 1 expected_current_hys_donor_id: description: >- Expected current hys donor id. Validation: required_unless:decision,source_record_merged, integer, min:0. Required unless decision is source_record_merged; zero represents no current donor. type: integer minimum: 0 example: 0 expected_claim_mapping_id: description: >- Expected claim mapping id. Validation: nullable, integer, min:1. type: integer minimum: 1 example: 1 nullable: true type: object oneOf: - required: - target_hys_donor_id - expected_current_hys_donor_id properties: decision: type: string enum: - match_separate_donor type: object - required: - decision properties: decision: type: string enum: - source_record_merged type: object responses: '200': description: Operation result. content: application/json: schema: properties: status: type: string example: success data: $ref: '#/components/schemas/IntegrationHubIdentityResolution' message: description: Operation receipt. type: string example: Example nullable: false 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. '404': description: >- Feature, connection, review evidence, donor or organization-owned record is unavailable. content: application/json: schema: $ref: '#/components/schemas/NotFoundResponse' '422': description: >- Request, stale review evidence, mapping claim, unsupported provider or selected state validation failed. content: application/json: schema: $ref: '#/components/schemas/RequestRejection' security: - bearerAuth: [] - apiKeyAuth: [] components: schemas: IntegrationHubIdentityResolution: description: >- Identity mapping result. Merge decisions never merge donor records or move gifts; missing-source retirement may clear only matching legacy source-id fields. Optional retirement fields vary by first/repeated result. oneOf: - properties: decision: type: string enum: - match_separate_donor idempotent: type: boolean example: true incoming_mapping: properties: id: description: Organization-owned record identifier. type: integer example: 42 nullable: false provider_object_id: description: Display value. type: string example: Example nullable: false hys_donor_id: description: Organization-owned record identifier. type: integer example: 42 nullable: false type: object moved_mapping: properties: id: description: Organization-owned record identifier. type: integer example: 42 nullable: false provider_object_id: description: Display value. type: string example: Example nullable: false hys_donor_id: description: Organization-owned record identifier. type: integer example: 42 nullable: false type: object nullable: true provider_object_ids_to_verify: type: array items: type: string type: object - properties: decision: type: string enum: - source_record_merged idempotent: type: boolean example: true mapping_retired: type: boolean example: true retired_mapping_id: description: Organization-owned record identifier. type: integer example: 42 nullable: true cleared_donor_source_fields: type: array items: type: string resolved_conflict_count: description: Count. type: integer minimum: 0 example: 2 provider_object_ids_to_verify: type: array items: type: string 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 NotFoundResponse: title: NotFoundResponse description: >- Returned with HTTP 404 when a resource lookup misses (typically because the id doesn't exist OR is scoped to a different `client_id`). Note: many endpoints intentionally collapse 'not found' and 'forbidden' into a single 404 to avoid leaking which records exist in another tenant. required: - message properties: message: description: >- Human-readable message. Often a more specific string like `Donor not found` or `Trip not found`. type: string example: Not Found 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.