Mailyte API · vv1
Three APIs, one account
Send transactional email, run marketing campaigns, and host mailboxes on your own domain — sharing one set of domains and one API key. 304 endpoints, no SDK required.
POST
/api/v1/messagescurl -X POST 'https://app.mailyte.com/api/v1/messages' \
-H 'Authorization: Bearer mk_live_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"to": "ada@example.com",
"from": "hello@yourdomain.com",
"subject": "Your receipt from Acme",
"html": "<h1>Thanks!</h1><p>Your order is on its way.</p>"
}'Pick the part you need
The three products share an account, your verified domains and one credential — but they are different jobs with different endpoints, so the documentation keeps them apart.
- Email API75 endpointsReceipts, password resets, notifications — the mail your application sends one message at a time, or five hundred at once. Submit over HTTP or relay over SMTP, then follow every message through delivery events and webhooks.If you have used Mailgun, Postmark or SendGrid, this is the part you know.
- Marketing53 endpointsBulk sends to an audience, with the things bulk mail is required to have: unsubscribe handling, audience management and reporting. Marketing mail rides a separate egress path from your transactional mail, so a newsletter cannot damage the reputation carrying your password resets.If you have used Mailchimp or Brevo, this is the part you know.
- Email hosting103 endpointsReal mailboxes with IMAP, SMTP and webmail. Provision them for a domain with your organization API key; read and send their mail with a mailbox token, which acts as one person rather than as the organization.If you have used Zoho Mail, Google Workspace or Microsoft 365, this is the part you know.
Whichever you are using
QuickstartAn API key to a delivered message in five minutes, including the three things that trip everyone up on a first attempt.AuthenticationAPI keys and scopes for your application; mailbox tokens for acting as one mailbox holder. When to use which.Help centreUsing Mailyte from the dashboard — billing, team roles, DNS setup. Written for people, not integrations.
Test in the SandboxSMTP and test keys that deliver nothing, simulated bounces, and an API to assert on what your app sent.ErrorsEvery status code, what causes it, and whether retrying will help.Webhook eventsThe full event catalogue and payloads, for delivery, bounces and complaints.Migrating hereEndpoint mapping from Mailgun, SendGrid and Postmark, plus the two steps people skip.