Quickstart

Create an account, verify a domain, make an API key, send. The first three steps happen once; after that, sending is a single request.

1. Create an account

Sign up for Anypost. Your account belongs to a team, and everything you create next, domains, API keys, sends, belongs to that team.

You can only send from a domain you have verified. In the dashboard, add the domain you will send from. Anypost shows you a few CNAME records; publish them at your DNS provider, then verify the domain.

Verification depends on DNS propagation, so it can take anywhere from a few minutes to a few hours. Domains & DNS setup covers the records and troubleshooting in full. You need one verified domain before step 4.

3. Create an API key

In the dashboard, create an API key. Copy the secret, which starts with ap_, when it is shown. It is shown once and cannot be retrieved later. This key authenticates both the HTTP API and SMTP. See Authentication for scoping and rotation.

4. Send an email

Send over the HTTP API. Use your verified domain in from and your key as the bearer token. Pick your language with the tabs:

curl https://api.anypost.com/v1/email \
  -H "Authorization: Bearer ap_AbCdEf12KxLmNoPq..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": "[email protected]",
    "to": ["[email protected]"],
    "subject": "Hello from Anypost",
    "text": "It worked."
  }'

A 202 response means the message was accepted:

{
  "id": "email_018f4f3e-7b2c-7c80-8e21-1a3a4f5b6c7d",
  "created_at": "2026-04-30T12:00:00.123000Z"
}

That is your first send. The 202 means Anypost has the message, not that it was delivered; delivery and engagement arrive later as events.

Sending over SMTP instead

The same message can go over SMTP. Authenticate with the username anypost and your ap_ key as the password. See Sending over SMTP for the host, ports, and TLS settings.

What's next