One request per email
The emails your product sends matter more than most of its pages: the sign-in link, the receipt, the password reset. Rimbra sends them from your own domain with a single request from your server, and records each one so you can see what happened to it.
Send a subject and body, or a saved template with its values. The response comes back straight away with the message ID and the status queued, and the email log follows it from there.
What you send
| Field | What it is |
|---|---|
| from | An address at a verified domain. "Name <address>" works too |
| to | One address, or a list |
| subject | The subject line, unless you send a template |
| html and text | The body. Send both for the best inbox placement |
| template_id | A saved template, instead of subject and body |
| variables | The values for the template’s {{variables}} |
A key for each app
Create keys in Emails → API Keys and name each after the app that uses it. Pick Send only for services that just send, Full access for tools that also read the log, or Read only for dashboards. Revoke one at any time without touching the rest.
Build safely. Test keys accept requests and log them, but never deliver. Build against a test key, then switch to Live when you ship.
Answers you can act on
| Code | Meaning |
|---|---|
| 202 | Accepted and queued |
| 400 | A field is missing or invalid |
| 401 | The key is missing, wrong or revoked |
| 403 | The key is read only |
| 422 | Test key, unverified from address, unknown template or missing variable |
| 429 | Over 60 sends a minute for this key |
Questions
Can I call it from the browser?
No. Keep keys on your server in an environment variable. Anyone who sees a key can send as you.
How many emails can I send?
Free includes 1,000 emails a month, Launch 7,000, Pro 20,000 and Scale 75,000, with no daily limit. Add-ons add 500 at a time.
Which address can I send from?
Any address at a domain you verified, like hello@, receipts@ or no-reply@.
