> ## Documentation Index > Fetch the complete documentation index at: https://ahasend.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > AhaSend stores all message data in the EU. See /facts. > The API base URL is https://api.ahasend.com. Send the API key in the Authorization: Bearer header. See /api-reference/authentication. > Use send.ahasend.com for SMTP. Ports 25, 587 and 2525 use STARTTLS. Port 465 is not supported. See /smtp. > For send-only integrations, create an API Key v2 under Credentials → Add and scope it to messages:send:{your-domain}. See /send-api/credentials and /api-reference/scopes. # Update a Campaign via the API > Change a draft AhaSend marketing campaign: its name, sender, reply-to, lists, subject, preview text or design. Only a draft campaign can be changed. The AhaSend API changes a draft campaign. Access requires `campaigns:write`. A campaign that is not a draft answers `409` with `campaign is not a draft`. To change a scheduled campaign, [unschedule it](/docs/api-reference/campaigns/unschedule-campaign) first. See [Changes only to drafts](/docs/api-reference/campaigns/overview#changes-only-to-drafts). **Fields:** * A field that you leave out does not change and is not checked. A request with no field is refused with `400`. * `null` clears `subject`, `preheader`, `from` or `reply_to`. When you clear `from`, `reply_to` stays. * `list_ids` replaces all lists of the campaign. A list that does not exist is refused with `400`. * `template_id` is not accepted: only [Create Campaign](/docs/api-reference/campaigns/create-campaign) can copy a campaign template. A request with `template_id` is refused with `400` as an unknown field. * The fields follow the rules of [Create Campaign](/docs/api-reference/campaigns/create-campaign). **Design:** * You cannot change the editor of the design. * A campaign with no design yet needs `content.mjml` or `content.html`, which sets its editor. * For a `simple` design, send only `content.text`: you can change the design only in the dashboard. * When you send a new `content.mjml` or `content.html` and leave out `content.text`, a text written by hand stays, and a text made from the HTML is made again from the new HTML. Send `content.text` as `null` to make the text again from the new HTML, also when the text was written by hand. * A text written by hand that stays must still render. If it holds a `{{`, `{%` or `{#` that cannot be rendered, the request is refused with `400`. * The content follows the content rules of [Create Campaign](/docs/api-reference/campaigns/create-campaign). **Changes from the dashboard:** * The API and the dashboard change the same campaign. The request waits for other changes to the same campaign to finish, and a send that starts after the request uses the change. * When a dashboard editor is open on the same campaign, the design that is saved last is kept. This operation accepts an `Idempotency-Key` header. A refusal from this operation is stored for the key, so send a corrected request with a new key. See [Idempotency](/docs/api-reference/idempotency) and [campaign retries](/docs/api-reference/campaigns/overview#idempotency). ## Related Guides * [API authentication](/docs/api-reference/authentication), [Permission scopes](/docs/api-reference/scopes), [Idempotency](/docs/api-reference/idempotency). * [Get Campaign](/docs/api-reference/campaigns/get-campaign), [API errors](/docs/api-reference/errors), [API rate limits](/docs/api-reference/rate-limits). ## OpenAPI ````yaml openapi.yaml PUT /v2/accounts/{account_id}/campaigns/{campaign_id} openapi: 3.1.0 info: title: AhaSend API v2 description: > The AhaSend API v2 allows you to send transactional emails, manage domains, webhooks, routes, API keys, and view statistics. ## Authentication All API requests must be authenticated using a Bearer token in the Authorization header: ``` Authorization: Bearer aha-sk-64-CHARACTER-RANDOM-STRING ``` ## Scopes API keys have specific scopes that control access to different resources and actions: ### Message Scopes - `messages:send:all` - Send messages from any domain in the account - `messages:send:{domain}` - Send messages from a specific domain - `messages:cancel:all` - Cancel messages from any domain - `messages:cancel:{domain}` - Cancel messages from a specific domain - `messages:read:all` - Read messages from any domain - `messages:read:{domain}` - Read messages from a specific domain ### Domain Scopes - `domains:read` - Read all domains - `domains:write` - Create and update domains - `domains:delete:all` - Delete any domain - `domains:delete:{domain}` - Delete a specific domain ### Account Scopes - `accounts:read` - Read account information - `accounts:write` - Update account settings - `accounts:billing` - Access billing information - `accounts:members:read` - Read account members - `accounts:members:add` - Add account members - `accounts:members:update` - Update account members - `accounts:members:remove` - Remove account members ### Webhook Scopes - `webhooks:read:all` - Read all webhooks - `webhooks:read:{domain}` - Read webhooks for a specific domain - `webhooks:write:all` - Create and update webhooks - `webhooks:write:{domain}` - Create and update webhooks for a specific domain - `webhooks:delete:all` - Delete any webhook - `webhooks:delete:{domain}` - Delete webhooks for a specific domain ### Route Scopes - `routes:read:all` - Read all routes - `routes:read:{domain}` - Read routes for a specific domain - `routes:write:all` - Create and update routes - `routes:write:{domain}` - Create and update routes for a specific domain - `routes:delete:all` - Delete any route - `routes:delete:{domain}` - Delete routes for a specific domain ### Suppression Scopes - `suppressions:read` - Read suppressions - `suppressions:write` - Create suppressions - `suppressions:delete` - Delete suppressions - `suppressions:wipe` - Delete the account's suppressions except protected ones (dangerous) ### Template Scopes - `templates:read` - Read transactional templates, their drafts and their published versions, and campaign templates - `templates:write` - Create and update transactional templates, and publish, discard and restore their drafts; create and update campaign templates - `templates:delete` - Delete transactional templates and campaign templates ### Campaign Scopes - `campaigns:read` - Read campaigns, their stats and their recipients - `campaigns:write` - Create, update and duplicate campaigns - `campaigns:delete` - Delete draft campaigns - `campaigns:send` - Send, unschedule and test-send campaigns ### Contact Scopes - `contacts:read` - Read contacts - `contacts:write` - Create and update contacts - `contacts:delete` - Delete contacts ### Contact lifecycle and attributes Contacts are account-global. A contact created through this API joins no list on its own; campaigns target lists, so add it to one with the Lists endpoints before a campaign can reach it. Contact subscription state and suppression records are independent: creating, updating, unsubscribing, resubscribing, or deleting a contact never creates, changes, or removes complaint, permanent, or protected suppressions. Prefer unsubscribe over delete when the goal is only to stop marketing mail, because unsubscribe is reversible and preserves contact history. Writable attribute keys and types come from the account's contact-attribute definitions managed in the dashboard; this API does not expose property definition CRUD. Writes accept only canonical values for those definitions, while reads remain legacy-safe and can return any recursively nested JSON value previously stored. An email used as `{id_or_email}` is a raw SDK argument and must be percent-encoded exactly once as a URL path segment by an HTTP client. For example, do not pre-encode `user+tag@example.com` before passing it to an SDK that encodes path parameters. ### List Scopes - `lists:read` - Read lists and list membership - `lists:write` - Create and update lists, and add or remove their contacts - `lists:delete` - Delete lists ### Lists and membership A list is a static, private, single opt-in container of contacts, and it is what a campaign targets. A membership carries its own `subscription_status` (`unconfirmed`, `confirmed`, `unsubscribed`, or `complained`), which is per-list consent and is independent of the contact's account-wide `unsubscribed` flag. A membership created without a status named is `confirmed`, because that is what a campaign reaches. `complained` is the mailbox provider's verdict, never writable, and a membership holding it is frozen. Deleting a list keeps its memberships, so an unsubscribe survives it. Removing a contact from a list deletes the membership row and discards that record with it, which is why unsubscribing is the reversible way to stop marketing mail on one list. Expanding a list's members with `include_contacts=true` requires `contacts:read` in addition to `lists:read`. ### SMTP Credentials Scopes - `smtp-credentials:read:all` - Read all SMTP credentials - `smtp-credentials:read:{domain}` - Read SMTP credentials for a specific domain - `smtp-credentials:write:all` - Create SMTP credentials - `smtp-credentials:write:{domain}` - Create SMTP credentials for a specific domain - `smtp-credentials:delete:all` - Delete any SMTP credentials - `smtp-credentials:delete:{domain}` - Delete SMTP credentials for a specific domain ### Statistics Scopes - `statistics-transactional:read:all` - Read all transactional statistics - `statistics-transactional:read:{domain}` - Read transactional statistics for a specific domain ### API Key Scopes - `api-keys:read` - Read API keys - `api-keys:write` - Create and update API keys - `api-keys:delete` - Delete API keys ### Sub-Account Scopes - `sub-accounts:read` - List and read sub accounts under the parent - `sub-accounts:write` - Create and update sub accounts - `sub-accounts:delete` - Soft-delete sub accounts - `sub-accounts:suspend` - Pause and resume sub accounts, and unpause their domains - `sub-accounts:usage` - Read per-sub-account usage and allocated cost - `sub-account-api-keys:read` - List and read API keys owned by sub accounts - `sub-account-api-keys:write` - Create and update API keys owned by sub accounts - `sub-account-api-keys:delete` - Delete API keys owned by sub accounts ## Rate Limiting - General API endpoints: 100 requests per second, 200 burst - Statistics endpoints: 1 request per second, 1 burst ## Pagination List endpoints use cursor-based pagination with the following parameters: - `limit`: Maximum number of items to return (default: 100, max: 100) - `after`: Pass `pagination.next_cursor` to fetch the next page - `before`: Pass `pagination.previous_cursor` to fetch the previous page `after` and `before` are mutually exclusive. A legacy `cursor` query may be accepted by parts of the server for backwards compatibility, but it is not part of the v2 public contract. ## Time Formats All timestamps must be in RFC3339 format, e.g., `2023-12-25T10:30:00Z` ## Idempotency The operations that explicitly declare the optional `Idempotency-Key` header support idempotency. Other POST operations do not gain idempotency implicitly. When the header is provided: - A fresh execution does not return `Idempotent-Replayed`. - A completed stored response is replayed with its original status and body and `Idempotent-Replayed: true`. - An unexpired in-progress execution returns HTTP 409 with `Idempotent-Replayed: false` and a positive integer `Retry-After` header. - Reusing a key with a different HTTP method, resolved request path, or request body returns HTTP 422. That response has neither `Idempotent-Replayed` nor `Retry-After`. - For ordinary idempotent operations, deterministic 2xx and 4xx outcomes produced after the idempotency middleware are stored and replayed. Authentication and IP-allow-list failures happen before idempotency and are therefore not stored. - The two secret-bearing API-key create operations use manual encrypted completion. They store and replay a successful 201, including the same one-time `secret_key`; a controller-produced 4xx is not stored and leaves the key in progress until its execution lease expires. - Server errors (5xx), handler failures, and panics are not stored. The key is released so retrying the same request with the same key re-executes it. The v2 API does not use an HTTP 412 failed-key tombstone. - Idempotency keys for non-secret responses expire after 24 hours. - Encrypted API-key creation replay responses expire after 5 minutes. ## IP Allow Lists Each API key can carry an `ip_allow_list`: a set of source IPs that restrict where the key may authenticate from. - Entries are CIDR blocks (e.g. `203.0.113.0/24`) or bare IPv4/IPv6 addresses (stored as a `/32` or `/128`). They are canonicalized and de-duplicated; the allow-all prefixes `0.0.0.0/0` and `::/0` are rejected, and at most 100 entries are allowed after de-duplication (a longer list is rejected with HTTP 400). - An empty list (the default) places no restriction. - When the list is non-empty, any authenticated request whose client IP is not covered by an entry is rejected with HTTP 403 on every v2 endpoint, regardless of the key's scopes. - Manage the list with the `ip_allow_list` field on the API-key create and update endpoints (including the sub-account API-key endpoints). - When a key updates its own `ip_allow_list` to a value that excludes the caller's current IP, the update is rejected with HTTP 409 to prevent self-lockout. Updating a sub-account key from a parent key has no such guard. version: 2.0.0 contact: email: support@ahasend.com license: name: MIT identifier: MIT servers: - url: https://api.ahasend.com description: Production server security: - BearerAuth: [] tags: - name: Utility description: Utility endpoints for health checks and diagnostics - name: API Keys description: Manage API keys for authentication and access control - name: Domains description: Manage sending domains - name: Messages description: Send and manage transactional messages - name: Accounts description: Manage account settings and members - name: Contacts description: Read, create, update, batch upsert, and delete account-global contacts - name: Templates description: >- Create, change, publish and delete the account's transactional templates, and read them with their drafts, their published versions and the variables a send must supply - name: Campaign Templates description: >- Create, change, read and delete the account's campaign templates, the designs a campaign copies when it is made from one - name: Campaigns description: >- Create, change, read, duplicate, delete, test and send the account's marketing campaigns, and read their stats and recipients - name: Lists description: Manage contact lists and the contacts on them - name: Suppressions description: Manage email suppressions - name: Routes description: Manage inbound email routing - name: Webhooks description: Manage webhook notifications - name: SMTP Credentials description: Manage SMTP authentication credentials - name: Statistics description: Access transactional email statistics - name: Message Events description: Webhooks for outbound message delivery events - name: Suppression Events description: Webhooks for suppression list changes - name: Domain Events description: Webhooks for domain configuration issues - name: Route Events description: Webhooks for inbound email routing paths: /v2/accounts/{account_id}/campaigns/{campaign_id}: put: tags: - Campaigns summary: Update Campaign description: | Changes a draft campaign. A field the request leaves out is neither changed nor checked, and `null` clears `subject`, `preheader`, `from` and `reply_to`. A campaign that is not a draft cannot be changed. The change waits for any other change of the same campaign, from the dashboard or the API, and a send that starts after it reads it. The design of a `simple` campaign can be changed only in the dashboard: send only `content.text` for one. Between this request and a dashboard editor open on the same campaign, the later design save wins. operationId: updateCampaign parameters: - name: account_id in: path required: true description: Account ID schema: type: string format: uuid - name: campaign_id in: path required: true description: Campaign ID schema: type: string format: uuid - $ref: '#/components/parameters/IdempotencyKey' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/UpdateCampaignRequest' responses: '200': description: Campaign updated headers: Idempotent-Replayed: $ref: '#/components/headers/IdempotentReplayed' content: application/json: schema: $ref: '#/components/schemas/Campaign' '400': description: >- Invalid campaign_id, an invalid body or field, a list that does not exist, or a request with no changes. The message names the field and the problem. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Missing `campaigns:write` scope content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Campaign not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': $ref: '#/components/responses/CampaignConflict' '422': $ref: '#/components/responses/IdempotencyPayloadMismatch' '429': description: Too many requests content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - BearerAuth: - campaigns:write x-code-samples: - lang: go label: AhaSend Go SDK source: | package main import ( "context" "fmt" "log" "os" "github.com/AhaSend/ahasend-go" "github.com/AhaSend/ahasend-go/api" "github.com/AhaSend/ahasend-go/models/requests" "github.com/google/uuid" ) func main() { client := api.NewAPIClient(api.WithAPIKey(os.Getenv("AHASEND_API_KEY"))) accountID := uuid.MustParse(os.Getenv("AHASEND_ACCOUNT_ID")) ctx := context.Background() campaignID := uuid.MustParse("11111111-1111-4111-8111-111111111111") // Only the fields you set change, and only while the campaign is a // draft. A ReplyTo that points at "" clears the reply-to address. response, _, err := client.CampaignsAPI.UpdateCampaign(ctx, accountID, campaignID, requests.UpdateCampaignRequest{ Subject: ahasend.String("Our news for October"), ReplyTo: ahasend.String(""), }) if err != nil { log.Fatalf("Error updating campaign: %v", err) } fmt.Printf("Updated campaign %s, %d issues left\n", response.Name, len(response.Issues)) } - lang: javascript label: Node.js 22+ (AhaSend SDK) source: > import { AhaSendClient } from "@ahasend/sdk"; const client = AhaSendClient.fromEnv(); // The SDK sends a fresh Idempotency-Key automatically and reuses it on its own retries. const campaignId = "00000000-0000-4000-8000-000000000014"; // Only a draft can change; null clears the reply-to address. const campaign = await client.campaigns.update(campaignId, { subject: "What we shipped in October", reply_to: null, }); console.log("Campaign updated.", { id: campaign.id, ready: campaign.ready }); components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: > Optional idempotency key for safe request retries. Must be a unique string for each logical request. An identical request with a completed stored outcome returns the original status and body. An in-progress execution returns 409, a changed method/path/body returns 422, and a released 5xx execution may run again. Keys for non-secret responses expire after 24 hours. API-key create responses include a one-time `secret_key`, so successful encrypted replay responses for those operations expire after 5 minutes. schema: type: string maxLength: 255 example: user-12345-create-domain-20240101 schemas: UpdateCampaignRequest: type: object additionalProperties: false description: | Changes to a draft campaign. A field left out is neither changed nor checked. The design's editor never changes. properties: name: type: string minLength: 1 maxLength: 255 description: Campaign name. Spaces around it are dropped. subject: type: - string - 'null' description: The subject line, cleaned as on create. Null clears it. preheader: type: - string - 'null' description: The preview text, cleaned as on create. Null clears it. from: oneOf: - $ref: '#/components/schemas/TemplateAddressInput' - type: 'null' description: >- The sender, as on create. Null clears the sender; `reply_to` stays as it is. reply_to: type: - string - 'null' format: email description: The reply-to address, as on create. Null clears it. list_ids: type: array minItems: 1 maxItems: 50 items: type: string format: uuid description: >- The lists to send to, which replace the campaign's lists, as on create. content: $ref: '#/components/schemas/TemplateContentInput' description: >- The content of the design, by the rules of `TemplateContentInput`, in the design's editor. For a `simple` design, send only `text`. A campaign with no design yet needs `mjml` or `html`, which sets its editor. Campaign: allOf: - $ref: '#/components/schemas/CampaignListItem' - type: object required: - list_ids - editor - content - ready - issues properties: list_ids: type: array items: type: string format: uuid description: >- The lists the campaign sends to, in the order they were saved. A list that was deleted is left out. editor: oneOf: - $ref: '#/components/schemas/TemplateEditor' - type: 'null' description: >- The editor of the campaign's design. Null while the campaign has no design. content: oneOf: - $ref: '#/components/schemas/TemplateContent' - type: 'null' description: >- The content of the campaign's design. Null while it has no design, or its design has neither HTML nor text. ready: type: - boolean - 'null' description: >- Whether the draft has no issue, so it can be sent. Null unless the campaign is a draft. issues: oneOf: - type: array items: $ref: '#/components/schemas/CampaignIssue' - type: 'null' description: >- The reasons the draft cannot be sent yet, in a fixed order; empty when it is ready. Null unless the campaign is a draft. ErrorResponse: type: object description: | Human-readable API error. The server currently sends no stable machine error code. In particular, clients must not parse `message` to distinguish IP-allow-list, scope, ownership, plan, self-lockout, suppression-duplicate, or other errors that share an HTTP status. additionalProperties: false required: - message properties: message: type: string description: Error description example: message: Error message TemplateAddressInput: type: object additionalProperties: false required: - email description: An address in a template write, in the shape a Template answers it. properties: email: type: string format: email description: The email address. name: type: string description: The display name. TemplateContentInput: type: object additionalProperties: false description: | The content of a template write. It holds at most one of `mjml` and `html`, and at least one of `mjml`, `html` and `text`. The `content` of an `advanced` or `html` draft, or of the Template when it has no draft, can be sent back as it is: an `mjml` or `html` equal to the current one is held to the size limit but not compiled again or held to the HTML checks, and keeps the stored HTML. While a draft exists, the Template's `content` is the published copy's, and sending it back replaces the draft's design. Leave `content` out of a write that does not change it. For a `simple` template, send back only `text`: its `html` can be changed only in the dashboard. The text follows these rules: - Beside a new `mjml` or `html`, a missing `text` keeps the draft's text when it is custom, and that text must still render, as a sent text must; otherwise, and on a create, it makes the text from the new HTML. A null `text` makes the text from the new HTML, and so does a `text` equal to a text made from an earlier HTML: the draft's made text, or the published copy's made text when the draft does not hold that text as custom. A read `content` can so be sent back with a changed design. Any other `text` is stored as made when it equals the text made from the new HTML, and as custom otherwise. To keep a made text beside a new design, send the design first and the text in a second request. - Otherwise a `text` equal to the draft's custom text keeps it; one equal to the text made from the draft's HTML is stored as made; any other is stored as custom. A null `text` makes the text again from the draft's HTML, and is refused when there is no HTML. Line ends written as CRLF are stored as LF, and a blank text is refused. `mjml`, `html` and a custom `text` each have a size limit. properties: mjml: type: string minLength: 1 description: | The MJML source. Only for `advanced` templates. It is compiled in strict mode, and every problem strict validation finds is refused with its line. Images must use full `https://` URLs: the API cannot upload files. html: type: string minLength: 1 description: | The HTML. Only for `html` templates; the HTML of a `simple` template can be changed only in the dashboard. Images and stylesheets must use full `https://` URLs: the API cannot upload files. text: type: - string - 'null' description: The plain text version. Null makes it from the HTML. text_is_custom: type: boolean description: >- Accepted so a read `content` can be sent back, and ignored. The text rules decide it. CampaignListItem: type: object required: - object - id - created_at - updated_at - name - subject - preheader - from - reply_to - status - status_reason - send_at - send_resumes_at - finished_at description: >- A campaign as List Campaigns returns it, without its lists, content and issues. properties: object: type: string enum: - campaign description: Object type identifier id: type: string format: uuid description: Campaign ID created_at: type: string format: date-time description: When the campaign was created updated_at: type: string format: date-time description: When the campaign's own fields last changed name: type: string description: >- Campaign name, as it appears in the dashboard. Recipients do not see it. subject: type: - string - 'null' description: The subject line. Null until one is set. preheader: type: - string - 'null' description: >- The preview text, which most inboxes show after the subject. Null until one is set. from: oneOf: - $ref: '#/components/schemas/Address' - type: 'null' description: >- The sender. Null until a complete sender is set, and when its domain was deleted. `name` is an empty string when the campaign has no sender name, so the object can be sent back as it is. reply_to: type: - string - 'null' format: email description: The reply-to address. Null when none is set. status: $ref: '#/components/schemas/CampaignStatus' status_reason: type: - string - 'null' description: >- Why the campaign is in its status, when there is a reason to give. Null otherwise. send_at: type: - string - 'null' format: date-time description: When the campaign sends or sent, in UTC. Null until it is scheduled. send_resumes_at: type: - string - 'null' format: date-time description: >- When a send that reached the account's daily marketing limit continues, in UTC. Null otherwise. finished_at: type: - string - 'null' format: date-time description: When the send ended, in UTC. Null until then. TemplateEditor: type: string enum: - advanced - simple - html description: | The editor the template is designed with. It never changes after the template is created. - `advanced`: designed in MJML, with the dashboard's advanced editor. - `simple`: designed with the dashboard's simple editor. Its HTML is made from the design and can be read but not changed through the API. - `html`: an HTML template, uploaded or written by hand. TemplateContent: type: object required: - text_is_custom description: | A template's content. A key that does not apply to the template's editor is left out, and so are `mjml`, `html` and `text` when they are empty. properties: mjml: type: string description: The MJML source. Only for `advanced` templates. html: type: string description: >- The HTML of an `html` template, or the HTML made from the design of a `simple` template. text: type: string description: The plain text version of the email. text_is_custom: type: boolean description: >- Whether the text was written rather than made from the HTML. A text made from the HTML is made again whenever the design changes. CampaignIssue: type: object required: - code - message description: A reason the campaign cannot be sent yet. properties: code: type: string enum: - sender_missing - lists_missing - subject_missing - preheader_missing - design_missing - text_broken - unsubscribe_link_missing description: > - `sender_missing`: the campaign has no complete sender, or its domain was deleted. - `lists_missing`: the campaign has no list that still exists. - `subject_missing`: the campaign has no subject. - `preheader_missing`: the campaign has no preview text. - `design_missing`: the campaign has no design, or its design has no HTML. - `text_broken`: the subject, the preview text or the design holds template syntax that cannot be rendered, so every message would fail. - `unsubscribe_link_missing`: the HTML does not use `{{ unsubscribe_url }}`, with or without filters. message: type: string description: What to do, in the words the dashboard uses. Address: type: object required: - email properties: email: type: string format: email description: >- Valid email address from a domain defined in your account with valid DNS records name: type: string description: Display name for the sender example: email: noreply@example.com name: Example Corp CampaignStatus: type: string enum: - draft - validating - waiting_for_review - scheduled - sending - paused - sent - canceled - failed description: | Where the campaign is in its life. Only a `draft` can be changed or deleted. - `draft`: being prepared. - `validating`: scheduled, and its lists are being checked. - `waiting_for_review`: held for a review before it sends. - `scheduled`: accepted, waiting for its send time. - `sending`: sending now. - `paused`: sending stopped for now; `status_reason` says why. - `sent`: every message was sent. - `canceled`: stopped before it finished; `status_reason` says why. - `failed`: could not be sent; `status_reason` says why. headers: IdempotentReplayed: description: > Indicates that this response is a stored replay of a previous identical request. When this header is absent, the response is not a stored replay. Ordinary fresh responses do not send `false`; that value is reserved for an in-progress 409. schema: type: string enum: - 'true' IdempotencyRetryAfter: description: | Positive whole number of seconds after which the in-progress execution lease may be retried with the same key and unchanged request. schema: type: integer minimum: 1 responses: CampaignConflict: description: | Either the campaign's status does not allow the request (for most requests, the campaign is not a draft; for an unschedule, it is not validating or scheduled, or it has queued mail), or an execution with this idempotency key is still in progress. The in-progress case is identified only by `Idempotent-Replayed: false` plus a positive integer `Retry-After`; retry it after that many seconds with the same key. A new status conflict has neither header; a stored replay of one has `Idempotent-Replayed: true` (a test send's status conflict is not stored, so it is never replayed). The message is not a stable discriminator. headers: Idempotent-Replayed: description: | `false` with a positive `Retry-After` means an execution is in progress. `true` means a stored status 409 was replayed. Absent means a fresh status conflict. schema: type: string enum: - 'true' - 'false' Retry-After: $ref: '#/components/headers/IdempotencyRetryAfter' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: message: campaign is not a draft IdempotencyPayloadMismatch: description: | Idempotency key was already used with a different HTTP method, resolved request path, or request body. This response includes neither `Idempotent-Replayed` nor `Retry-After`. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: message: idempotency key was already used with a different request payload securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: aha-sk-64-CHARACTER-RANDOM-STRING description: | API key for authentication. Non-empty Security Requirement values are AhaSend API-key roles. Roles listed within one requirement object are jointly required; separate requirement objects are alternatives. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.