The eComms API
What the public eComms surface solves, what to expect from a call, and where to start.
An HTTP surface for sending transactional email from your own backend: authenticate with an
API key, make one call, and get every address’s admission result on the spot. No SDK to
install, no session, and no :orgId in the URL — the key already says which organization the
send belongs to.
Admitting is not delivering. The response comes back the moment the send is accepted, with
every address resolved to claimed or suppressed; what happens afterwards — deliveries,
bounces, complaints — arrives by webhook, or you can look it up whenever you like.
Where to go next
QuickstartFrom no account to a delivered email, step by step.AuthenticationWhere a key comes from, the shape of the token, and how to revoke it.Send an emailThe body, the response and the errors of the call that does the work.Retrieve a sendThe delivery state of an address already admitted.WebhooksHear about deliveries, bounces and complaints as they happen.ErrorsThe closed set of codes any response can carry.