API and webhooks
Let your own software read and send mail through DMU Mail, with keys that carry only the permissions you give them, and webhooks that tell you when mail or contacts change.
What it does
Connect your own software
Keys with narrow permissions
Start from Read only, Read and send or Full access, or tick each permission yourself.
Read, write and send
List and read conversations, reply, send, schedule, label, assign and close, and keep contacts in step.
Webhooks, not polling
Get an event when mail arrives or goes, a conversation is closed, assigned or moved, or a contact changes.
Signed and retried
Every webhook is signed so you can check it, and a failed one is tried again, eight attempts over about a day.
How it works
From key to first request
- 1
Create a key
An administrator opens Settings › API keys, names the key after what will use it, chooses a preset and copies the key. It is shown once.
- 2
Call the API
Send the key in an Authorization header. It acts as the administrator who made it, and reaches the mailboxes that person can.
- 3
Add a webhook
Give DMU Mail an address and choose the events, then keep the signing secret to check each request.
Good to know
The details
- Who can use it
- Administrators create keys and webhooks. During the beta, every organisation has the API.
- Where
- Settings › API keys, and its Webhooks tab. The full reference is in the API docs on this site.
- Limits
- Each key can make 120 requests a minute, up to 30 of them sends. An organisation can have 10 webhooks.
- Safety
- A key never reaches more than the administrator who made it, and stops working if they leave. Only a scrambled copy is stored, so we can’t show it again.
- Not in the API yet
- Inviting and removing people. There is no sandbox either: mail you send through the API really goes.
Be one of the first teams in
We let a few organisations into the private beta every week. Join the waitlist and we’ll email you when there’s room for your team.
Three quick questions. No card needed.