New to email on the platform? Start with Introduction to email for send types, billing, and deliverability basics.
Email on Arowana is channel-based: each workspace configures one or more email channels with their own from identity, domain verification, and supported message types (MESSAGE, NEWSLETTER). Nothing is a global shared sender—every brand keeps its own reputation boundary.

​
What you configure in the product

You provide display name, from address, and complete domain authentication (SPF, DKIM, DMARC) as required by your provider path. Until the domain is verified, production sends for that channel may be blocked or limited.

​
Deliverability features

The email channel is built for scale and reputation:
AreaBehavior
SuppressionBounces and complaints feed suppression lists; pre-send checks avoid sending to bad addresses.
Provider eventsDelivered, bounced, opened, clicked, complained—surfaced in logs, analytics, and optionally developer webhooks.
UnsubscribeMarketing mail includes compliant one-click unsubscribe where required; flows respect opt-out state.

​
Billing

Email is billed as Basic Message units for both MESSAGE and NEWSLETTER—there is no separate “long email” tier like RCS Single vs Basic. See Billing (Email) and Billing (RCS) for the contrast.

​
API surface

Programmatic sends use POST /v1/messages with email-specific fields documented at Action-based email and Subscription email. Status and timeline use GET /v1/messages/{id} the same as RCS.

Action-based (MESSAGE)

API examples for action-based email sends.

Subscription (NEWSLETTER)

API examples for subscription and campaign sends.