Verify API Update: RCS Support Now Available

The  Verify API now supports RCS (Rich Communication Services) as a new channel for verifying your users. This update enables a faster, richer, and more engaging authentication experience while increasing security and conversion rates.

Why Use RCS for User Verification?

RCS is often called the next generation of SMS. It allows applications or services to send interactive messages with advanced capabilities such as:

• Rich media and branded content, including images, logos, and fully customized templates.

• Suggested replies and action buttons, simplifying user interactions and one-tap approvals.

• Read receipts and delivery status, providing better visibility into the authentication flow.

How RCS Improves the Verify API Experience

Verify API simplifies your user verification workflow by supporting multiple channels to suit every device and user. RCS now joins SMS, voice, and other existing options as a rich, interactive channel that enhances the experience. 

Here’s what happens when you enable RCS:

1. The API first checks if the user’s device and carrier support RCS.

2. If RCS is available, a rich message with a one-tap verification link or action button is sent.

3. If RCS is not supported, Verify falls back to the next channel specified in the Verify request workflow.

Getting Started with RCS in Verify API

Include a new “rcs” channel entry in the workflow list to enable RCS in your Verify API requests. Here’s a quick example in cURL:

{
   "locale": "es-es",
   "brand": "ACME",
   "workflow": [
      {
         "channel": "rcs",
         "to": "34600000000",
         "from": "agentname"
      },
      {
         "channel": "sms",
         "to": "34600000000"
      }
   ]
}

That’s it. Verify will take care of delivering a rich authentication experience automatically. If RCS isn’t supported on the user’s device or carrier, Verify API will switch to SMS.

Ready to Try it?

Visit the Verify API documentation to explore the full setup guide and start integrating RCS into your authentication workflows.