Skip to main content
POST
AhaSend Go SDK
The AhaSend API creates an API key owned by the sub-account. Parent credentials must belong to the parent account and include sub-account-api-keys:write; sub-account credentials cannot manage nested API keys. The returned secret_key authenticates as the child account and should be stored immediately. Bootstrap example:
  1. Create the sub-account with POST /v2/accounts/{account_id}/sub-accounts and a unique Idempotency-Key.
  2. Create the bootstrap child API key with this endpoint and a different unique Idempotency-Key.
  3. Store the one-time secret_key from the 201 response. Exact idempotent replays within 5 minutes return the same secret_key.
  4. Use that child secret with the child sub_account_id as the account_id on ordinary v2 routes.
Plan availability: sub-accounts are included on Pro (up to 9) and Max (no limit). There is no charge per sub-account; the volume of all sub-accounts is pooled on the parent’s plan. See plans and features.

Authorizations

Authorization
string
header
required

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.

Headers

Idempotency-Key
string

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.

Maximum string length: 255

Path Parameters

account_id
string<uuid>
required

Parent account ID

sub_account_id
string<uuid>
required

Sub account ID

Body

application/json
label
string
required

Human-readable label for the API key; must not be empty

Required string length: 1 - 255
scopes
string[]
required

Array of scope strings to grant to this API key

Minimum array length: 1
ip_allow_list
string[]

Optional list of source IPs allowed to authenticate with this key. Each entry is a CIDR block (e.g. 203.0.113.0/24) or a bare IPv4/IPv6 address (stored as a /32 or /128). Entries are canonicalized (host bits are masked) 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. Omit the field or pass an empty array to leave the key usable from any IP.

Response

Sub-account API key created successfully

object
enum<string>
required

Object type identifier

Available options:
api_key
id
string<uuid>
required

Unique identifier for the API key

created_at
string<date-time>
required

When the API key was created

updated_at
string<date-time>
required

When the API key was last updated

last_used_at
string<date-time> | null
required

When the API key was last used (updates every 5-10 minutes)

account_id
string<uuid>
required

Account ID this API key belongs to

label
string
required

Human-readable label for the API key

public_key
string
required

Public portion of the API key

scopes
object[]
required

Scopes granted to this API key

ip_allow_list
string[]
required

Source IPs allowed to authenticate with this API key, as canonical CIDR blocks (a bare address is stored as a /32 for IPv4 or /128 for IPv6). Always present; an empty array means the key may be used from any source IP. When non-empty, an 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.

secret_key
string
required
read-only

One-time secret key. Store it immediately. Exact successful idempotent replays return the same secret during the 5-minute encrypted replay window.