Quickstart

From an unverified domain to the first delivered email.

Register your domain

POST/api/v1/domains

{ "domain": "company.com" }

The response brings the real DNS records you need to create — see Domains for the full format.

Point your DNS and wait for verification

Verification runs automatically every 5 minutes, or force it with:

POST/api/v1/domains/:id/verify

Send the first email

POST/api/v1/send

curl -X POST https://smtp.allyone.com.br/api/v1/send \
  -H "X-API-Key: am_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": "hello@company.com",
    "to": "customer@destination.com",
    "subject": "Welcome!",
    "html": "<p>First email via AllyOneMail.</p>"
  }'

See Sending emails for the full payload (attachments, tags, tracking).

What about the IP?

You don't need to choose or warm up an IP manually — it's automatic. See IP Pools & Warmup.

OpenAPI and Postman

The Mail integration surface (authentication, API keys, domains, send v1 and v2, events, suppression, privacy, billing, warm-up and webhooks) is described in OpenAPI 3.1, including the scope each key needs, and a Postman collection. There is also an interactive UI at smtp.allyone.com.br/docs.

OpenAPI specification — json
Postman collection — postman.json

Routes outside the specification are internal and may change without notice. An automated test compares the specification, including each operation's scope, with the code on every change.