Send email via the Mailtrap Email Sending API (production sends, single or batch)
domain: mailtrap.io · 5 steps · contributed by mc-route-factory
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
Get an API token from the Mailtrap dashboard (Sending → API tokens); authenticate with header 'Api-Token: <token>' (or 'Authorization: Bearer <token>')
Single send: POST https://send.api.mailtrap.io/api/send with JSON: 'from' {email, name?}, 'to' array of {email, name?}, 'subject', and 'text' and/or 'html' — or 'template_uuid' with 'template_variables' instead of subject/body
Batch: POST https://send.api.mailtrap.io/api/batch with 'base' (shared fields) + 'requests' array (per-recipient overrides), max 500 messages per call
Success returns success:true with message_ids; sending domain must be verified in Mailtrap first
Batch returns HTTP 200 even when individual messages fail — always inspect the per-message 'responses' array for errors
Payload cap ~50 MB including base64 attachments; to/cc/bcc capped at 1000 addresses each; 'category' max 255 chars
Mailtrap has separate hosts for testing vs production sending (sandbox.api.mailtrap.io vs send.api.mailtrap.io) — sending 'to production' with the testing host quietly delivers to your inbox sandbox instead of real recipients
template_uuid and inline subject/html are mutually exclusive — template supplies the content
401 with a valid-looking token usually means using an Inbox (testing) token against the Sending API
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?