Skip to main content
Email in Crevio is two things: a simple way to broadcast to your customers, and a full email client — inboxes, threads, messages, drafts, search, and replies — that lets you (or an agent) run your inbox programmatically. Use the broadcast side to blast an announcement to every paid customer, and the client side to read, reply to, and label inbound mail. You can just ask Crevio to draft and send a launch email, or wire up an agent that watches for incoming messages and replies on your behalf.

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.
FieldPurpose
toArray of explicit recipient addresses
subjectEmail subject
bodyEmail body
customer_typeRecipient filter (e.g. paid, free, lead)
send_to_alltrue to send to all matching customers
fromOverride the sending address

Worked example: broadcast to all paid customers

Let Crevio write the copy: ask it to draft the broadcast, review the draft, then send. See Tasks.

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.
The client also supports reply-all and forward on a message, the same way.

Drafts, search, and labels

Attachments are available on messages, and drafts can be sent once finalized.

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 from hello@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 to email_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.