AhaSend API v2

Name: AhaSend API v2 API
Brand: AhaSend API v2
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliverybearer41 EndpointsREST

For Agents

Send transactional emails, manage sending domains, configure webhooks and routes, and read delivery stats through a scoped bearer-token API.

Install Jentic One Beta

Connect the AhaSend API v2 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AhaSend API v2, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AhaSend API v2 API.

Send transactional and conversational messages with full RFC822 fields and idempotency keys

Create, verify, and delete sending domains tied to an account

Issue and revoke scoped API keys for messages, domains, webhooks, and suppressions

GET STARTED

Start building with AhaSend API v2 API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for AhaSend API v2, keeping it validated and agent-ready. AhaSend is a transactional email platform; the v2 API exposes 41 endpoints for sending messages, managing sending domains and SMTP credentials, configuring webhooks and routes, handling suppressions, and reading transactional statistics. Authentication uses bearer API keys prefixed with aha-sk- and supports fine-grained scopes per resource (messages, domains, webhooks, suppressions). General endpoints allow 100 requests per second with 200 burst, while statistics endpoints are limited to 1 request per second.

Use Cases

Patterns agents use AhaSend API v2 API for, with concrete tasks.

★ Transactional Email Sending

Backend services send transactional messages - receipts, password resets, notifications - through POST /v2/accounts/{account_id}/messages. Idempotency keys are supported via the Idempotency-Key header so retries do not duplicate sends, and timestamps follow RFC3339. The 100 req/sec general rate limit accommodates high-volume bursts without bespoke retry logic.

POST /v2/accounts/{account_id}/messages with from, to, subject, html_body, and an Idempotency-Key

Domain and Credential Management

Operations teams script domain onboarding by creating a sending domain, retrieving DNS records to publish, and verifying once DNS is in place. The same flow can issue scoped SMTP credentials and API keys with resource-level scopes (e.g. messages:send:{domain}), keeping each integration's blast radius small. Old credentials are deleted via the matching endpoints when integrations are retired.

POST /v2/accounts/{account_id}/domains with the domain name, then call GET to fetch DNS records for verification

Webhook and Route Orchestration

AhaSend webhooks deliver delivery, open, click, and bounce events to a customer endpoint, while routes forward inbound mail. Through POST /v2/accounts/{account_id}/webhooks an integration can subscribe a target URL with the event types of interest, and POST /v2/accounts/{account_id}/routes wires up inbound parsing for reply-handling features.

POST /v2/accounts/{account_id}/webhooks with target_url and selected event types

Suppression and Compliance

Compliance teams keep the suppression list accurate by reading current entries, adding manual suppressions for legal or fraud reasons, and removing suppressions when an address has been re-confirmed. The /suppressions/all delete endpoint is destructive and intended only for full clears. Suppression scopes (suppressions:wipe) gate access to that risky operation.

GET /v2/accounts/{account_id}/suppressions then DELETE the entry for hello@example.com

AI Agent Email Operations via Jentic

An agent built on Jentic can send transactional mail or manage suppressions in response to natural-language requests. Jentic stores the AhaSend bearer key (with whatever scopes you provision) in its vault and applies it at request time, so the agent never sees the raw aha-sk- value or has to reason about which scope is needed.

Use Jentic to search 'send a transactional email', execute POST /v2/accounts/{account_id}/messages with the message body

Key Endpoints

41 endpoints — jentic publishes the only available openapi specification for ahasend api v2, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/accounts/{account_id}/messages

Send a transactional message

GET

/v2/accounts/{account_id}/messages/{message_id}

Get a message by ID

DELETE

/v2/accounts/{account_id}/messages/{message_id}/cancel

Cancel a scheduled message

POST

/v2/accounts/{account_id}/domains

Create a sending domain

POST

/v2/accounts/{account_id}/webhooks

Create a webhook subscription

POST

/v2/accounts/{account_id}/routes

Create an inbound route

POST

/v2/accounts/{account_id}/suppressions

Create a suppression

POST

/v2/accounts/{account_id}/api-keys

Create a scoped API key

POST

/v2/accounts/{account_id}/messages

Send a transactional message

GET

/v2/accounts/{account_id}/messages/{message_id}

Get a message by ID

DELETE

/v2/accounts/{account_id}/messages/{message_id}/cancel

Cancel a scheduled message

POST

/v2/accounts/{account_id}/domains

Create a sending domain

POST

/v2/accounts/{account_id}/webhooks

Create a webhook subscription

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your AhaSend bearer key is stored once, encrypted, by your own Jentic One instance and attached at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a transactional email' or 'create a webhook', and Jentic returns the matching AhaSend operation with its input schema, including the account_id path parameter, so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using AhaSend API v2 API through Jentic.

Why is there no official OpenAPI spec for AhaSend API v2?

AhaSend publishes a YAML spec for documentation but Jentic generates and maintains the validated, bundled OpenAPI specification used here so that AI agents and developers can call the AhaSend API v2 via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the AhaSend API v2 use?

Bearer authentication using a 64-character API key prefixed with aha-sk- in the Authorization header. Keys carry scopes such as messages:send:{domain}, webhooks:write, and suppressions:wipe. Through Jentic, the key is held in the credential vault and injected at request time.

What are the rate limits for the AhaSend API v2?

General API endpoints allow 100 requests per second with a burst of 200; statistics endpoints are limited to 1 request per second with a burst of 1. Plan polling and reporting jobs accordingly - pull stats on a schedule rather than per send.

How do I send a transactional email through the AhaSend API v2?

POST /v2/accounts/{account_id}/messages with the from address, recipients, subject, and either html_body or text_body. Include an Idempotency-Key header to make retries safe. The response includes a message_id you can use with GET /v2/accounts/{account_id}/messages/{message_id} for status.

How do I send transactional email through Jentic?

Search Jentic for 'send a transactional email'. Load the POST /v2/accounts/{account_id}/messages schema, supply the account ID, sender, recipient, subject, and body, and execute. Jentic injects the bearer key with the right scope and returns the message_id.

Can I cancel a scheduled message before it sends?

Yes. Call DELETE /v2/accounts/{account_id}/messages/{message_id}/cancel before delivery starts. Once a message has been sent, cancellation no longer applies and the response will indicate the message is in a terminal state.

Can I limit what my agent is allowed to do with the AhaSend API?

Yes. Because Jentic One is self-hosted, the rules you set on your own instance decide which AhaSend operations and credentials the agent may use. Since AhaSend puts the account ID in the URL path (/v2/accounts/{account_id}/...), you can pin the agent to a single account, and you choose the exact operations it can call, such as sending a message via POST /v2/accounts/{account_id}/messages. Operations like cancelling a message or creating a scoped API key stay off limits unless you explicitly grant them.

AhaSend API v2

Connect the AhaSend API v2 to your agent

Capabilities

Start building with AhaSend API v2 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs