> ## 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. # Set the organization primary donor profile > Sets the organization’s primary donor HysForm. The profile must be active, organization-owned and type donor. Repeated selection retains that primary profile; unavailable profiles return 404. ## OpenAPI ````yaml put /admin/forms/{hysform_id}/primary 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/forms/{hysform_id}/primary: put: tags: - Donors summary: Set the organization primary donor profile description: >- Sets the organization’s primary donor HysForm. The profile must be active, organization-owned and type donor. Repeated selection retains that primary profile; unavailable profiles return 404. operationId: DonorPrimaryProfileController_update parameters: - name: hysform_id in: path description: Record ID in the authenticated organization. required: true schema: type: integer example: 42 example: 42 responses: '200': description: Set the organization primary donor profile completed. content: application/json: schema: properties: message: description: Confirmation. type: string example: Primary donor profile updated. data: $ref: '#/components/schemas/Hysform' type: object '401': description: Authentication is required. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Insufficient permission or feature access. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Resource not found in the organization or feature unavailable. content: application/json: schema: $ref: '#/components/schemas/NotFoundResponse' security: - bearerAuth: [] - apiKeyAuth: [] components: schemas: Hysform: title: Hysform description: >- Custom form definition. HysForms power donor profile forms and entity (recipient) profile forms. Historical `submit` forms formerly powered archived updates; existing records remain readable but their configuration is read-only after the legacy Progress Reports retirement. Each form has many `Field` records that describe individual inputs. The `standardized_fields_rollout_state` column is part of an in-flight migration that promotes commonly-used custom fields (first_name, phone, address, etc.) into real database columns. required: - id - client_id - name - type properties: id: description: Internal HysForm ID. type: integer format: int64 example: 42 client_id: description: Owning client. type: integer format: int64 example: 207 name: description: Display name. type: string example: Donor Profile — Standard type: description: >- Form purpose: `donor` for donor profiles, `entity` for recipient profiles, and historical `submit` archived-update definitions. Existing `submit` definitions are read-only compatibility metadata and new ones cannot be created. type: string enum: - donor - entity - submit example: donor do_not_email: description: >- Suppresses automated email triggers tied to this form. Raw legacy records may serialize boolean, integer or string flags. oneOf: - type: boolean nullable: true - type: integer enum: - 0 - 1 - type: string enum: - '0' - '1' - '' do_not_require_email: description: >- Allows form submissions without an email address. Raw legacy records may serialize boolean, integer or string flags. oneOf: - type: boolean nullable: true - type: integer enum: - 0 - 1 - type: string enum: - '0' - '1' - '' use_standardized_fields: description: >- Backwards-compat boolean for the standardized-fields rollout. Real state is in `standardized_fields_rollout_state`. type: boolean example: true nullable: true standardized_fields_rollout_state: description: >- Current stage in the standardized fields rollout: legacy = JSON-only, dual_write = writes to both, standardized_primary = standard columns are canonical. type: string enum: - legacy - dual_write - standardized_primary - null example: dual_write nullable: true standardized_fields_enabled_at: description: When standardized fields were first enabled for this form. type: string format: date-time example: '2026-02-10T17:30:00Z' nullable: true standardized_fields_verified_at: description: >- When a verification pass last confirmed the standardized columns match the json values. type: string format: date-time example: '2026-02-12T09:00:00Z' nullable: true created_at: type: string format: date-time example: '2025-01-15T08:00:00Z' updated_at: type: string format: date-time example: '2026-02-12T09:00:00Z' deleted_at: type: string format: date-time example: null 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 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 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.