Email on the platform is not a single global sender: each workspace configures one or more email channels with their own sender identity, domain verification, and supported message types.

​
Send types

TypeFriendly nameTypical use
MESSAGEAction-based emailOrder confirmations, password resets, account alerts — triggered by a user action or system event
NEWSLETTERSubscription emailCampaigns, newsletters, announcements — sent to opted-in subscriber lists
More send types (such as conversational email) will be added as the channel evolves. Both map to channel configuration in the dashboard; the Developer API targets a specific channel and template when sending programmatically.

​
Billing

Email sends are billed as Basic Message units for both MESSAGE and NEWSLETTER — there is no Basic vs Single split by content length (unlike RCS). Email has its own independent tier: volume on the email channel does not affect your RCS or SMS pricing. Responses still include billing metadata for reconciliation.

​
Deliverability

The platform integrates with best-in-class email delivery infrastructure. Operational features include suppression checks, bounce and complaint handling, and webhook events (delivered, opened, clicked) that feed analytics and your developer webhooks.

​
API usage

Use POST /v1/messages with email-specific fields (recipient, subject, HTML/text or template reference). Auth, balance checks, queueing, and webhooks follow the same pattern as RCS. See the Email API for the full field reference. See Email (API) for endpoint-oriented documentation.