POST /v1/rcs/agents
Creates a draft RCS agent. Two fields — region and use_case — are permanent after the agent is submitted for review and cannot be changed afterwards. billing_category can be updated via PATCH /v1/rcs/agents/{id} before the agent is launched. Once the draft is created, use PATCH /v1/rcs/agents/{id} to fill in the agent’s brand profile (logo, color, contact info, etc.) before submitting.

​
Request

​
Authorization
string
required
Bearer <api_key>
{
  "display_name": "FreshFood Official",
  "region": "EUROPE",
  "billing_category": "NON_CONVERSATIONAL",
  "use_case": "PROMOTIONAL",
  "newsletter_enabled": true
}
​
display_name
string
required
Brand name displayed to end users in the RCS messaging app. Typically matches your registered brand name.
​
region
string
required
Where the agent operates and where its data is stored.
ValueCoverage
EUROPEEurope (the only region currently supported by Arowana)
Additional regions (North America, Asia Pacific) are on the roadmap. For now all agents must use EUROPE.
The region cannot be changed after the agent is created. Create a new agent if you need a different region.
​
billing_category
string
required
Determines how Google bills for messages sent by this agent.
ValueDescription
CONVERSATIONALMulti-turn back-and-forth conversations billed per 24-hour session.
NON_CONVERSATIONALOne-way notifications billed per individual message (consolidates the legacy Basic Message and Single Message categories).
billing_category can be updated via PATCH /v1/rcs/agents/{id} at any time before the agent is launched. After launch, contact support to request a change.
​
use_case
string
required
Categorises the agent and determines which message types Google permits it to send.
ValueAllowed message typesTypical use
OTPMESSAGE onlyOne-time passwords for auth or transaction confirmation. No promotional content.
TRANSACTIONALMESSAGE, CONVERSATIONDelivery alerts, account notifications, purchase confirmations. No promotional content.
PROMOTIONALMESSAGE, NEWSLETTERMarketing campaigns and offers. Can use MAU billing with newsletter_enabled.
MULTI_USEMESSAGE, CONVERSATION, NEWSLETTERCombines transactional and promotional content. Broadest coverage.
We recommend MULTI_USE for most agents. It covers the widest range of message types — transactional alerts, conversations, and newsletter broadcasts — without needing separate agents per use case. Only choose a narrower use case if you have a specific compliance or business reason.
The use case cannot be changed after the agent is submitted for launch.
​
newsletter_enabled
boolean
Set to true to enable the NEWSLETTER message type and MAU subscriber billing on this agent. This flag is part of the Google submission and cannot be added retroactively — if you omit it now, you must create a new agent to get newsletter capability later.See Newsletter enablement for consent and billing details.

​
Response

{
  "agent_id": "ag_draft_a1b2c3",
  "status": "DRAFT",
  "display_name": "FreshFood Official",
  "region": "EUROPE",
  "billing_category": "NON_CONVERSATIONAL",
  "use_case": "PROMOTIONAL",
  "newsletter_enabled": true,
  "created_at": "2026-03-28T09:00:00Z"
}
​
agent_id
string
Use this ID for all subsequent agent operations: profile updates, submission, and status checks.
​
status
string
Always DRAFT on creation. Transitions once you call POST /v1/rcs/agents/{id}/submit.

​
Agent lifecycle

DRAFT ──(fill profile)──▶ DRAFT
     ──(submit)──────────▶ PENDING_REVIEW
                               │
                    ┌──────────┴──────────┐
                    ▼                     ▼
                APPROVED              REJECTED
            (carrier launch)    (edit + resubmit)
After creation the agent profile is incomplete (DRAFT). Fill in branding, contact, and compliance fields via PATCH /v1/rcs/agents/{id} before submitting.

Update agent profile

Add logo, color, contact info, and compliance URLs before submitting.

Submit for review

Submit a complete draft agent for Google / carrier review.