Part 1 — Broadcast and transactional send
POST /emails sends an email to your customers. Filter recipients by customer_type or send to everyone with send_to_all. from defaults to your account’s default sending address.
| Field | Purpose |
|---|---|
to | Array of explicit recipient addresses |
subject | Email subject |
body | Email body |
customer_type | Recipient filter (e.g. paid, free, lead) |
send_to_all | true to send to all matching customers |
from | Override the sending address |
Worked example: broadcast to all paid customers
Part 2 — The email client
Crevio also operates as a real mailbox built around inboxes → threads → messages, with drafts, search, labels, and attachments.Inboxes, threads, and messages
Worked example: reply to an inbound message
Reading a thread gives you its messages; reply directly to one.reply-all and forward on a message, the same way.
Drafts, search, and labels
Sending domains
To send from your own domain (rather than the platform default), add a sending domain and verify it. This is what makes broadcasts arrive fromhello@yourbrand.com.
You’ll add the DNS records the response gives you at your registrar. If the domain is managed by Crevio, you can do that via the Domains zone-records API.
Email webhooks
The inbox is event-driven. Subscribe toemail_message.* events to react to mail in real time instead of polling:
email_message.received, email_message.sent, email_message.delivered, email_message.bounced, email_message.complained, email_message.failed.
A common pattern: listen for email_message.received, run a Task to draft a reply, and send it. See Webhooks.
Next steps
Webhooks
React to inbound mail with
email_message.* events.Tasks
Let an agent triage and reply to your inbox.
Customers
Segment who your broadcasts reach.
Domains
Manage DNS for your sending domain.

