Integrations
For developers: send and receive email from your application with the HTTP API or an AI agent skill — and let your team manage the replies in the Inbox. Official framework SDKs are on the way.
Not a developer? See how the inbox works →
Available nowThe fastest way to start — call the REST API directly from any language.
Request
curl -X POST https://api.mailngine.com/v1/emails \
-H "Authorization: Bearer mn_live_xxxxx" \
-H "Content-Type: application/json" \
-d '{
"from": "[email protected]",
"to": ["[email protected]"],
"subject": "Welcome to Mailngine",
"html": "<h1>Welcome!</h1><p>Thanks for signing up.</p>",
"text": "Welcome! Thanks for signing up."
}'Response
{
"data": {
"id": "9b2f8c1e-4d3a-4f6b-9c2e-1a7d5e8f0b3c",
"from": "[email protected]",
"to": ["[email protected]"],
"subject": "Welcome to Mailngine",
"status": "queued",
"message_id": "<[email protected]>",
"created_at": "2026-06-02T10:30:00Z"
}
}Email that comes back
Mailngine handles both directions. Set a reply_to and add your own metadata, and when the recipient replies you get it two ways: a signed email.received webhook correlated back to your records, and the conversation waiting in your team's Inbox — properly threaded.
- Inbound mail fires an HMAC-signed
email.receivedwebhook. - Replies are correlated to the message you sent via
metadata. - The same reply lands in the team Inbox, threaded into the conversation.
curl -X POST https://api.mailngine.com/v1/emails \
-H "Authorization: Bearer mn_live_xxxxx" \
-H "Content-Type: application/json" \
-d '{
"from": "[email protected]",
"to": ["[email protected]"],
"reply_to": "[email protected]",
"subject": "Your support request",
"text": "We received your message and will get back to you.",
"metadata": { "ticket_id": "T-1234" }
}'Official SDKs — Coming Soon
We are actively building official libraries so you can install and send in one line. Until they ship, the HTTP API works everywhere. Want to help? Contributions are welcome on GitHub.