Per-account API keys
Created by the account admin, scoped, shown only once and revocable at any time.
Developers
The API is yours. So are the limits.
Each account creates its own API keys and sends transactional email, SMS and push over HTTP, with open documentation. What hasn't changed is why the API has limits: abuse brings down everyone's delivery.
The limits
Every key has a rate limit, and every account has a monthly quota per channel. It isn't a billing detail: it's what stops a leaked key or a bad list from taking down the infrastructure's reputation — and every customer's delivery depends on that reputation.
Today
What you can already do.
Transactional email over HTTP
`POST /v1/emails/send` and batch sending, signed with your domain's DKIM. SMS and push have their own endpoints — SMS is still in validation.
Public documentation
The API reference for the platform, business email, CRM and Pages, open to anyone who wants to read it before subscribing.
Roadmap
What isn't open yet.
Event webhooks for your account
Event delivery exists in the infrastructure; the screen for you to register your endpoints doesn't yet. Today, the configurable webhooks are the CRM's lead destinations.
Marketing and support APIs
They don't accept your key yet. First, their authorization has to pass the same proof the others already passed.