Sending RCS rich cards

A rich card combines media, text, and suggested actions into a single structured message. Recipients see the card as a native UI element in their messaging client, providing an app-like experience. Use rich cards to present information that encourages interaction, such as product details, booking confirmations, or promotional offers.

To group multiple cards into a scrollable set, see Sending RCS carousels.

When to use a rich card

Rich cards are well suited for messages that benefit from a visual layout with interactive elements. Common use cases include:

If your message requires only text with optional suggestions, use a Sending RCS text messages instead. If you need to send a file without additional card structure, see Sending RCS file messages.

Rich card components

A standalone rich card consists of the following components. At least one of Media, Title, or Description is required in CardContent.

Card orientation

The CardOrientation field controls the layout relationship between media and text content. This field is required.

Media and heights

The Media object contains a FileUrl (required), an optional ThumbnailUrl, and an optional Height value. The FileUrl must match the pattern ^(https://|s3://).+$ and can be a maximum of 2,000 characters. The maximum media file size is 100 MB.

For details on supported media formats, delivery options, and S3 presigned URLs, see Sending RCS file messages.

Card-level suggestions

You can attach up to 4 suggestions to a rich card by including them in the CardContent.Suggestions array. Card-level suggestions appear directly below the card content.

In addition to card-level suggestions, you can include up to 11 message-level suggestions in the top-level Suggestions array of the RcsMessageContent structure. Message-level suggestions appear as persistent chips below the entire message.

For the full list of suggestion types (including Reply, OpenUrl, DialPhone, ShowLocation, RequestLocation, and CreateCalendarEvent), see Configuring RCS suggestions.

RcsMessageContent structure

The following JSON shows the structure of the RcsMessageContent parameter for a standalone rich card. Pass this JSON as a string to the --rcs-message-content parameter in the AWS CLI or as the RcsMessageContent parameter in the SDK.

{
  "Content": {
    "RichCard": {
      "StandaloneCard": {
        "CardOrientation": "VERTICAL",
        "CardContent": {
          "Title": "Your card title",
          "Description": "Additional details about the card content.",
          "Media": {
            "FileUrl": "https://example.com/image.jpg",
            "ThumbnailUrl": "https://example.com/thumb.jpg",
            "Height": "MEDIUM"
          },
          "Suggestions": [
            {
              "Reply": {
                "Text": "Confirm",
                "PostbackData": "confirm_action"
              }
            },
            {
              "OpenUrl": {
                "Text": "View details",
                "PostbackData": "view_details",
                "Url": "https://www.example.com/details"
              }
            }
          ]
        }
      }
    }
  },
  "Suggestions": [
    {
      "Reply": {
        "Text": "Help",
        "PostbackData": "help_menu"
      }
    }
  ]
}

In this structure:

Sending a rich card

Use the SendRcsMessage API action to send a rich card. Specify your pool or AWS RCS Agent as the --origination-identity and pass the rich card JSON structure as the --rcs-message-content parameter.

Cross-platform rendering

Rich card rendering varies between Android and iOS devices. Follow these recommendations for consistent results:

Rich card limits