> ## 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. # Create a donation-type email template variant > Creates or returns a donation-type-specific automated email template. Ordinary variants clone the default; DAF grant, IRA / QCD and explicitly contextual DAF advisor acknowledgments start with source-specific content and remain turned off until reviewed. DAF advisor and Direct soft-credit uses share the soft_credit template. Requires the admin API auth middleware and user permission checks. ## OpenAPI ````yaml post /admin/auto_emails/template/variant 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 sponsorship relationships, lifecycle transitions, and sponsorship-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: Client description: Client - name: Email Settings description: Email Settings - name: Admin Dashboard description: Admin Dashboard - name: Historical Archived Updates description: Historical Archived Updates - name: Team & access description: Team & access - name: Files description: Files - name: Wrapped description: Wrapped - name: Donor SignUp description: Donor SignUp - name: Frontend description: Frontend - name: User description: User paths: /admin/auto_emails/template/variant: post: tags: - Communications summary: Create a donation-type email template variant description: >- Creates or returns a donation-type-specific automated email template. Ordinary variants clone the default; DAF grant, IRA / QCD and explicitly contextual DAF advisor acknowledgments start with source-specific content and remain turned off until reviewed. DAF advisor and Direct soft-credit uses share the soft_credit template. Requires the admin API auth middleware and user permission checks. operationId: adc259a8cb4fe738588f4d7c0ec024d9 requestBody: description: >- Variant creation payload. The controller validates `emailset_id`, `trigger`, and `donation_type`, then scopes the lookup to the authenticated client. required: true content: application/json: schema: required: - emailset_id - trigger - donation_type properties: emailset_id: description: 'Email set ID. Validation rule: `required|integer`.' type: integer example: 42 trigger: description: >- Template trigger to clone. Validation rule: `required|string`. type: string example: pay_receipt donation_type: description: >- Variant key to create. DAF grant and IRA / QCD variants are created turned off. Validation rule: `required|string|in:in_kind,soft_credit,daf,qcd`. type: string enum: - in_kind - soft_credit - daf - qcd example: in_kind receipt_context: description: >- Use giving_source=daf and recipient_role=soft_credit with donation_type=soft_credit to create a disabled DAF advisor thank-you starter. Existing rows are returned without rewriting and include source_template_setup_issue when still copied from Standard. Missing context preserves ordinary Direct clone behavior. properties: giving_source: type: string enum: - direct - daf - qcd example: daf recipient_role: type: string enum: - primary - soft_credit example: soft_credit type: object nullable: true additionalProperties: false type: object responses: '200': description: The requested variant already existed. content: application/json: schema: properties: emailtemplate: description: Existing Emailtemplate model for the requested variant. type: object type: object '201': description: Variant created with ordinary or source-specific starting content. content: application/json: schema: properties: emailtemplate: description: >- New Emailtemplate model; source acknowledgments use separate starting content and remain disabled. type: object message: description: Confirmation message. type: string example: Variant created successfully. type: object '401': description: Missing or invalid API key or bearer token. content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' '422': description: Variant payload validation failed. content: application/json: schema: $ref: '#/components/schemas/ValidationErrorResponse' security: - bearerAuth: [] - apiKeyAuth: [] components: schemas: 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 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.