How do RCS APIs and webhooks work?
Published By Olov Elofsson2 min read
An RCS API lets your systems request a message to be sent. Webhooks receive later events such as delivery, read status and customer replies. The API accepting the request does not yet mean the phone has received the message.
Store the message identifier together with the order or case. When an event comes back, you can then update the right record. Verify the origin of the webhook call before the event is processed.
Addresses, fields and authentication depend on the provider. Use the documentation for the service you connect to. If SMS is to be the fallback, the integration also needs to know when it may be sent and how a pending RCS message is handled without sending duplicates.
Two directions in the same flow
The send request and the reply live for different lengths of time. An order system can request the message now while the phone's delivery report arrives later. The integration therefore needs to be able to find the same order without the original call still being open. Describe what each status may change and what should happen if an event is missing. This makes troubleshooting much clearer than a single label that says sent.
Sources (6)
- Google Messages: Common questions about RCS chats support.google.com
- Google RCS for Business: Send messages developers.google.com
- Google RCS for Business: Receive events developers.google.com
- Google RCS for Business: Webhooks developers.google.com
- Google RCS for Business: Capability checks developers.google.com
- Google RCS for Business: Best practices developers.google.com
Send RCS for your business
From 0,316 SEK per message. No setup fee or lock-in period.