Documentation
RCSSMS
RCSSMS
  1. Messages
  • RCS INTRODUCTION
  • RCS Message Support
  • Messages
    • Text
      POST
    • Text Suggestions
      POST
    • Stand Alone Card
      POST
    • Carousel Card
      POST
    • Media
      POST
  • FAQ
    • Frequently Asked Questions
  • Webhook
    • Webhook
  1. Messages

Text

Developing
POST
https://rest.qikberry.ai/v1/rcs/messages
The simplest messages are made of text. Text messages are best suited to communicate information without the need for visuals, complex interaction, or response.

✅ Supported Features#

Plain text up to 2,000 characters (varies by carrier)
Basic line breaks (\n)
Unicode character support
Delivery and read receipts (if enabled by user)
Fallback to SMS if RCS is unavailable (optional)Media and PDF files
When you send a message with an image, video, audio, or PDF file, your agent must provide a publicly accessible URL for the content or directly upload the file. For media files, you can also specify a thumbnail image that lets users preview the content before clicking on it. For audio files, the default audio widget is used as a placeholder.

Example#

The following code sends a plain text message. For formatting and value options, see phones.agentMessages.create.

Request

Header Params

Body Params application/json

Examples
{
    "to": "<MOBILE>",
    "agentID": "<AGENT_ID>",
    "message": {
        "templateId": "<TEMPLATE_ID>"
    }
}

Responses

🟢200Success
application/json
Body

Example
{
    "message": "1 numbers accepted",
    "data": [
        {
            "messageId": "a8XXXXXX-1bXX-4XXd-b5XX-5dXXXXXX:1",
            "mobile": "+9198XXXXXXXXX",
            "charges": 0.05
        }
    ]
}
🟠400Bad Request
🟠401Unauthorized
Modified at 2025-06-02 10:52:21
Previous
RCS Message Support
Next
Text Suggestions
Built with