Skip to content

Every customer gets an inbox.

Your app gives each customer an address on your domain, and an agent to answer it. Verify the domain once. Each new customer is then a call or two.

One shared inbox mixes every customer's mail.

And any key on it reaches all of them. Give each customer a box: their mail, their key and their agent stay apart.

  • One call per customer

    Make the address and tag it with your own id. Filter by it later with metadata[customerId].
  • A key for one box

    POST /v1/agents gives the customer's agent a key that reaches their inbox only. Other inboxes answer 404. Its first mail to a new address waits for someone on your team, unless it's a reply to a verified sender in the same thread on an open desk. A person turns that on, per inbox.
  • One webhook for everyone

    Each new-mail event carries data.inbox, so one endpoint can serve every customer.

Two ways to lay it out.

Both use the same domain and the same API. Pick by who holds the keys and whether you bill per customer.

For each customerTagged inboxes, one projectA project per customer
Set up withPOST /v1/inboxesPOST /v1/projects
A key that only reaches itan agent's key with inboxIdsan agent's key in that project
Usage to bill itNoGET /v1/projects/:id/usage
A daily send limitNolimits.sendPerDay
Best whenyou run every agent yourselfyou bill by use or hand out keys

A new customer, in a call or two.

Verify the domain once. After that, this is all a new customer takes. Your server's key makes these calls, and the agent only gets its own key.

curl -X POST https://api.drin.run/v1/inboxes \
  -H "Authorization: Bearer $DRIN_KEY" \
  -H 'content-type: application/json' \
  -d '{ "address": "c42@mail.yourapp.com", "domainId": "<mail.yourapp.com>",
        "displayName": "Customer 42", "metadata": { "customerId": "c_42" } }'

# Later, find it by your own id
GET /v1/inboxes?metadata[customerId]=c_42

Your first customer, today.

Verify your domain, make an inbox and point an agent at it.