Arowana lets marketing teams and developers send email, RCS, and SMS through a single API and campaign builder — without webhook plumbing, cron jobs, or carrier negotiation handled on your side. The Guides tab covers onboarding, concepts, and quickstarts. The API reference tab documents HTTP routes, parameters, and payloads with inline field documentation.

​
Start here

Pick the path that matches what you want to build:

Email campaign

Domain verification → list import → template → newsletter send.

RCS campaign

Sandbox → agent approval → contacts → template → launch.

Multi-channel campaign

Combine email and RCS in one flow with condition-based routing.

Consent sync

Import, capture, sync, and audit consent across all channels.

​
Quickstarts

Email

Send your first action-based email through a verified domain in minutes.

RCS sandbox

Verify a device and send real RCS through the Test Agent — no agent approval needed.

Webhooks

Register an HTTPS endpoint and verify signed delivery events.

Billing

Read balance, interpret send metadata, and set up auto-reload.

​
Learn

Use the sidebar Learn groups to understand billing, channel behaviour, and automation before building. Start with Billing units and Channel message types for the shared model, then go deeper per channel.

Billing units

Basic, Single, Conversation, MAU — and how tier volume works.

Channel message types

MESSAGE, CONVERSATION, NEWSLETTER mapped to billing units across email, RCS, and SMS.

Email capabilities

Channels, sender domains, deliverability, and suppression.

Billing (Email)

Email as a flat Basic Message unit and tier volume.

RCS messaging types

Content shapes, billing units, and traffic classification.

Billing (RCS)

Basic/Single split, conversation sessions, and newsletter MAU.

RCS agents

Production agents, approval, newsletter enablement, and the Test Agent.

Templating

Versions, brand kits, and channel constraints.

Campaigns in depth

Triggers, execution states, pause/resume, and API integration.

Events & analytics

Delivery, engagement, and lifecycle event streams.

Contacts

PII, consent, tags, segments, and channel addresses.

Landing pages

Forms, consent capture, hosting, and handoff to campaigns.

​
Concepts

Email

Channels, message types, deliverability, and suppression overview.

RCS

Agents, content types, traffic classification, and the Test Agent.

REST API

Gateway, workers, request lifecycle, and versioning.

Our philosophy

Errors you can act on, billing transparency, and time-to-first message.

​
API reference

Start at API overview. Under Messages, each page documents a specific channel and content shape with example payloads and billing rules. Messages overview links to every send variant and explains the billing object returned on every successful send.