Developers · RCS
Program rich messaging where RCS is enabled
Send RCS messages with richer layout and suggested actions — orchestrated alongside SMS fallback on Azmarq, where your account and device reach allow.
Built for: Engagement engineers adding branded rich messaging
- Rich cards & actions
- SMS fallback mindset
- Journey-ready
What you can build
01
Rich outbound
Media, suggested replies, and branded experiences versus plain SMS — subject to RCS reach.
02
Fallback planning
Design for SMS fallback when RCS isn’t available on the handset or route.
03
Console + API
Operate creatives in product surfaces; trigger sends from your backend where API access is enabled.
Quick start
01
Enable RCS on the account
Confirm agent/brand setup and entitlements with Azmarq (Google Partner stack).
02
Get API credentials
Issue keys for environments that are allowed to send RCS.
03
Send a test rich message
Target a device known to support RCS; verify fallback behaviour.
04
Subscribe to events
Use webhooks for delivery and suggested-action responses where supported.
Auth
Credentials from your console
RCS availability is account- and reach-dependent. Confirm live payloads and fallback fields in console documentation — samples are illustrative.
Illustrative rich send (shape only)
httpPOST /v1/rcs/messages
Authorization: Bearer <AZMARQ_API_KEY>
Content-Type: application/json
{
"to": "+9198XXXXXXXX",
"content": {
"type": "text",
"text": "Your order is on the way",
"suggestions": [{ "type": "reply", "text": "Track" }]
},
"sms_fallback": { "body": "Your order is on the way. Track: https://…" }
}
# Confirm agent IDs, media limits, and fallback rules in-console.Illustrative only — not a live contract. Confirm paths and fields in developers.azmarq.com.
Common use cases
Branded promotions
Richer creatives than SMS for campaigns that still need a fallback path.
Service updates
Shipping and status messages with tap actions.
Journey steps
Trigger RCS from Customer Journeys or your orchestration layer.
FAQs
RCS API — FAQs
Integration basics, credentials, and how this API relates to the product console.
Talk to salesNo — design with SMS fallback. RCS reach depends on device, agent setup, and routing.
Enablement is account-dependent. Confirm with Azmarq before building production RCS sends.
Build on RCS
Grab credentials in the console, or talk to sales if you need channel enablement, WhatsApp WABA setup, or SMPP packaging.
