Versioning
The version is part of the URL path. v1 is the current stable version. Within v1 we add new endpoints and optional fields without breaking existing integrations. Any breaking change ships under a new path version, and v1 keeps working while you migrate. Theversion field in the health response reports the build of the service, so it can change between deployments even within v1.
Authentication
Send your API key as a bearer token. Each key has a scope that limits what it can do:
A request with a missing, invalid or revoked key returns
401. A request with a valid key that lacks the scope for the action returns 403. See Security.
Endpoints
Emails
Domains
Keys, webhooks and usage
Webhook endpoints are managed in the dashboard. Events are delivered as described in Webhooks.
Conventions
- Errors are JSON with a
detailfield. See Errors, retries and limits. - Idempotency: send an
Idempotency-Keyheader with send and batch requests so a retry never sends twice. - Timestamps are ISO 8601 in UTC, for example
2026-09-01T09:00:00Z. - Rate limits apply per API key, per second, and depend on your plan. Daily and monthly quotas apply per account.