Cc, Bcc, scheduling and batches
Everything past the single send, with what each one costs and how it fails.
Several recipients
to, cc and bcc each take one address or a list, and Name <address> is accepted. Every person gets their own copy: each is its own email with its own id, status and webhooks, and each is charged as one email. Every copy shows the To and Cc lines; nobody sees Bcc. An address listed twice is sent to once, and 50 recipients is the most one send reaches.
curl -X POST https://api.woyra.io/v1/emails -H "Authorization: Bearer $WOYRA_KEY" -H 'Content-Type: application/json' -H 'Idempotency-Key: receipt-77' -d '{
"from": "Selam Pay <receipts@yourdomain.com>",
"to": ["alex@example.com"],
"cc": "finance@example.com",
"bcc": "archive@yourdomain.com",
"reply_to": "help@yourdomain.com",
"subject": "Your receipt",
"html": "<p>Thanks for your order.</p>"
}'The answer is the first copy, with a recipients list naming every copy's id. A recipient on your suppression list is skipped and shows as suppressed there; the others still go.
Reply-To and headers
reply_to sends replies somewhere other than from. headers adds your own: List-Unsubscribe and List-Unsubscribe-Post for one-click unsubscribe, which Gmail and Yahoo require of bulk senders, or an X- header your own systems read. Headers Woyra writes itself, such as From, Subject and Message-ID, cannot be set, nor any X-Woyra- header, and a line break in a name or value is refused.
"headers": {
"List-Unsubscribe": "<https://yourapp.com/unsubscribe/u_9912>",
"List-Unsubscribe-Post": "List-Unsubscribe=One-Click"
}Send later
scheduled_at holds the email until then, up to 30 days ahead. It is accepted, checked and priced now, with status scheduled, so a problem is reported when you send it, not when it was due. Until it leaves you can cancel it, and everything accepting it took comes back: the money held for it, any free allowance it used, and its place in today's sending limit.
# Tomorrow at eight
curl -X POST https://api.woyra.io/v1/emails -H "Authorization: Bearer $WOYRA_KEY" -H 'Content-Type: application/json' -H 'Idempotency-Key: reminder-12' -d '{"from": "hello@yourdomain.com", "to": "alex@example.com",
"subject": "Your appointment", "text": "See you at ten.",
"scheduled_at": "2026-10-10T08:00:00Z"}'
# Changed your mind
curl -X POST https://api.woyra.io/v1/emails/email_01J.../cancel -H "Authorization: Bearer $WOYRA_KEY"Batches
POST /v1/emails/batch takes a JSON array of up to 100 emails, each shaped exactly like a single send, reaching at most 1,000 recipients in all. A batch is all or nothing: every email is checked first, and one bad field refuses the whole batch with param naming which, such as [3].to. One Idempotency-Key covers it, so retrying a batch that timed out never sends it twice.
curl -X POST https://api.woyra.io/v1/emails/batch -H "Authorization: Bearer $WOYRA_KEY" -H 'Content-Type: application/json' -H 'Idempotency-Key: digest-2026-10-09' -d '[
{"from": "hello@yourdomain.com", "to": "alex@example.com", "subject": "Your week", "text": "..."},
{"from": "hello@yourdomain.com", "to": "sara@example.com", "subject": "Your week", "text": "..."}
]'Questions
Is an email to three people charged once or three times?
Three times: it is three emails, each delivered, tracked and reported on its own. That is also how every mailbox provider counts it.
Can I cancel a scheduled email at the last second?
Until the moment it starts to leave. Once the dispatcher has picked it up, cancelling answers that it is already being sent.
Do webhooks fire for scheduled and cancelled emails?
A scheduled email sends email.sent when it leaves, like any other. Cancelling one sends email.canceled.
Next
Get a test key and run any of this in about ninety seconds.