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

Stand Alone Card

Developing
POST
https://rest.qikberry.ai/v1/rcs/messages
A Rich Card is a visually enhanced message format in RCS Business Messaging that allows brands to sendcard can contain the following:
A. Media (image, GIF, or video)
B. Title text
C. Description text
D. Suggested replies and actions.
Rich cards create a more engaging and interactive user experience than simple SMS or RCS text messages.
A rich card can contain all of the listed items, but a card must contain at least an image, video, or title to be valid. A rich card can contain a maximum of four suggested actions or suggested replies.

Rich cards components#

[A] Media
Rich cards can include various media, such as images, GIFs, and videos. Rich cards support a variety of media formats.
Supported image types:
JPEG/JPG
GIF
PNG
Supported video types:
H.263
M4V
MP4
MPEG
MPEG-4
WebM
You can choose between three media heights for a rich card:
HeightDescription
SHORT112 DP - Small thumbnail-like image (useful for compact messages)
MEDIUM168 DP - Default size — balanced between visibility and space
TALL264 DP - Large image that takes up more vertical space — good for visual impact
rich-card-heights.png
Note: Regardless of height, the image should maintain a good aspect ratio and resolution. Poor-quality or oddly-sized images may appear distorted depending on device and carrier.
[B] Title
The title of a rich card acts like a headline—designed to capture the user's attention and quickly convey the purpose of your message. Keep it concise, informative, and within 200 characters.
[C] Description
The rich card description provides essential supporting information. It expands on the title, highlights key benefits, and encourages user action with a clear call to action. Descriptions can be up to 2,000 characters in length.
[D] Suggested replies and actions
Suggested replies help users interact with your agent in ways that it can easily respond to. Unless the interaction requires a freeform response, use suggested replies. They're easier to process than freeform text and they allow your agent to steer conversations down an optimal path.Suggested replies can be up to 25 characters long.
suggested-replies.png
Suggested actions allow an agent to hook into native device actions and they provide a tightly integrated experience for the user. When relevant, suggested actions can make it easy to call customer support or find a location on the map.
But don't overwhelm users with options. Only provide actions that are related to the most recent message, and only provide as many actions as necessary. Limit the number of suggested actions and suggested replies to what is useful to the user in a given context.

Example#

The following code sends a stand alone rich card with an image and suggested replies. For formatting and value options, see RichCard.

Request

Header Params

Body Params application/json

Examples
{
    "to": "<MOBILE>",
    "agentID": "<AGENT_ID>",
    "message": {
        "templateId": "<TEMPLATE_ID>",
        "templateParams": {
            "media": {
                "contentInfo": {
                    "fileUrl": "<FILE_URL>",
                    "fileName": "<FILE_TYPE>",
                    "mimeType": "<MIME_TYPE>"
                }
            }
        } 
    }
}

Responses

🟢200Success
application/json
Body

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