Use case

Email for agencies & platforms

Managing email for ten clients on one shared account means one leaked key or one bounce spike affects everyone. Sub-accounts give each client real isolation — without ten separate contracts.

The shared-account problem

One API key for every client means one compromised key exposes every client's sending. One shared domain reputation means one client's spam complaints can suppress deliverability for everyone else. Sub-accounts fix both: each client gets its own API keys, its own verified domains, and its own quota, carved from a pool you manage centrally — isolation without the overhead of a separate EuroMail account, invoice, and login per client.

Provision

One call per client

Create a sub-account with a name, a contact email, and a monthly quota drawn from the parent's pool. It gets its own dashboard login, its own API keys, and its own domain verification — a client's team can log in and see only their own sending, never another client's. Nesting stops at one level, so a sub-account can't spin up sub-accounts of its own.

curl -X POST https://api.euromail.dev/v1/accounts \
  -H "X-EuroMail-Api-Key: em_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Client A",
    "email": "[email protected]",
    "password": "securepassword123",
    "monthly_quota": 5000
  }'
Plan
Business or Enterprise (not Free)
Sub-account cap
5 on Business, unlimited on Enterprise
Nesting
One level only
Inherits
Parent's plan tier
API scope
sub_accounts:manage

Related

Start sending free Read the sub-accounts guide