developers
PilotReceipts and resets, over a small API.
The Send API is working and in private pilot. Transactional mail sent through it runs in its own lane, on its own IP pool, away from your newsletters.
send one message
One request. One credit.
A 202 means we’ve accepted it and reserved a credit. If it’s rejected before it leaves, the credit comes back.
requestPilot
curl https://sendapi.meereach.com/v1/messages \
-H "Authorization: Bearer $MEEREACH_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-4411-receipt" \
-d '{
"type": "transactional",
"to": "ada@example.com",
"from": { "email": "orders@northfieldsupply.com", "name": "Northfield Supply" },
"templateId": "8c1e2f4a-7b3d-4e5f-9a1b-2c3d4e5f6a7b",
"variables": { "first_name": "Ada", "order_number": "4411" }
}'HTTP/1.1 202 AcceptedWhat’s in the pilot.
- Idempotency
- Every send takes an Idempotency-Key. Retry as often as your network needs; the message goes once.
- Scoped keys
- Keys carry only the permissions you give them, can expire, are shown once and can be revoked.
- Templates
- Send inline HTML and text, or a stored template with variables filled in by Liquid.
- Events
- Look up a message, or page through its events: delivered, bounced, opened, clicked and more.
- Webhooks
- Signed with a timestamp, retried on failure, with a stable delivery ID so you can de-duplicate.
- Reference
- An OpenAPI description of every endpoint comes with pilot access.
What we don’t do yet
Build around these, or tell us which one you need first.
- Not yetSMTP relay
- REST only.
- Not yetAttachments, CC and BCC
- Not yetBatch sends
- One recipient per request.
- Not yetSDKs
- Plain HTTP for now.
- Not yetA webhook screen in the console
- Webhooks are managed through the API.
- Not yetThe automation flag in events
- Events don’t yet say whether a machine opened or clicked.