DEVELOPER HUB
API reference
for the real integration.
Find the request shapes, response states and safeguards your application needs before it sends.
Start with the contract
Use the OpenAPI document for machine-readable routes and the developer guide for the decision sequence. API keys stay on your server and should be scoped to the sending domain.
Core request groups
- Account, domain and approved template setup
- Application event proof and Stripe verification
- Validation, sending, idempotency and delivery logs
- Signed webhooks and bounded retries
Common implementation path
Install a versioned SDK, connect a real event, validate the exact recipient and template, then send with a stable idempotency key. A 202 response means queued; follow the returned message through logs or signed webhooks.
Sending reference · Retry guidance · Node.js guide · Python guide
YOUR NEXT STEP
Bring your idea.
We’ll help with the email.
Create an account. Choose your first email. Get guided through the setup.