Add a sending domain
Register a domain and start SES DKIM verification. The response carries the identity as created — verified is false, because nothing is verified until the DKIM records are published in the domain's DNS and SES resolves them. Poll /api/v1/domains/{id}/verify after publishing them.
region pins the SES region. The first domain a project adds LOCKS the project to that region and every later domain must match it — a project split across regions would have its SES configuration diverge silently.
stream assigns the identity to transactional or marketing traffic at creation; omit it to leave the identity serving both. stream_default makes it the project's default for that stream and therefore requires stream — sending it alone answers 422 validation_error rather than being ignored.
A host already registered — to this project or to another — answers 409 conflict when the caller can already send from it and 403 project_access_denied when it belongs elsewhere. A subdomain whose registrable root is held by a suspended project is refused the same way.
Requires the domains:write scope — Add and remove sending domains, and trigger verification.
Request
- Base URL: https://api.sendly.now
- URL: https://api.sendly.now/api/v1/domains
- Auth: one of:
- HTTP bearer
- API key in cookie better-auth.session_token
- OAuth 2 (authorization code, authorization URL https://app.sendly.now/api/auth/oauth2/authorize, token URL https://app.sendly.now/api/auth/oauth2/token, scopes: domains:write)
Request body
Response
The registered sending domain, awaiting DNS
Changes
No recorded changes to this operation across all 1 revision of this API.