Send email
Send transactional email through the project’s regional API. Boundry supports HTML, text alternatives, CC, BCC, reply-to, tags, attachments and idempotency keys.
Before you send
Verify the domain The From address must use a verified sending domain in this project.
Create an API key Keys are scoped to the project’s regional data plane.
Make an idempotent request Send Idempotency-Key when retries are possible.
Build the message
Provide one or more recipients, a subject and either html or text. Supply both formats whenever possible so recipients with restrictive mail clients still receive a readable message.
{
"from": "Acme <hello@mail.acme.com>",
"to": "customer@example.com",
"subject": "Your receipt",
"text": "Thanks for your order."
}Handle retries safely
Network failures do not tell you whether the service accepted a send. Add an Idempotency-Key header to retries: Boundry returns the original email ID rather than creating a duplicate message.
curl -X POST https://api.au.boundry.dev/emails \
-H "Authorization: Bearer $BOUNDRY_API_KEY" \
-H "Idempotency-Key: order-2847-receipt" \
-H "Content-Type: application/json" \
-d @email.jsonInspect the result
Every accepted message has an ID. View it in the dashboard to see its content, provider status and chronological events. Use webhooks when your application needs those events without polling.
Read the send-email endpoint →