For platforms
Inboxes inside your product.
Create, warm and monitor inboxes for your users through one API. We run the servers behind it.
POST /v1/inboxes
curl https://api.mailyard.com/v1/inboxes \
-H "Authorization: Bearer $MAILYARD_KEY" \
-d tenant=acct_2041 \
-d domain=getacme.co \
-d pattern="{first}.{last}" \
-d count=50{
"data": {
"batch": "bat_7k2m9x",
"inboxes": 50,
"status": "provisioning",
"ready_in_seconds": 240
}
}Built for platforms
Ship email infrastructure without running it.
Your users get inboxes. You never touch a mail server.
One call per batch
Create inboxes for a user with a single request.
Live webhooks
Signed events when inboxes, domains or IPs change.
Isolated per tenant
Each of your customers gets its own IP pool.
Pay for what you use
Billed per active inbox, at volume prices.
How it fits
You own the product. We own the pipes.
Mailyard sits between your app and the inbox providers.
Your product
Your user asks for inboxes.
Our mail servers
Send from IP pools we own.
Your user’s sequencer
Gets SMTP and IMAP details.
FAQ
Platform questions.
Talk to the engineers who run the servers.
No. Inboxes are created under your account and your users only see your product. Sending runs on our servers.
Build it on our servers.
Get a sandbox key and an engineer on a call.