sinch-api-messages-send-card

Send RCS rich card messages with title, image, and buttons via Sinch Conversation API.

6|2|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-messages-send-card-sinch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-api-messages-send-card
Source: https://github.com/sinch/sinch-plugins/tree/main/plugins/sinch-antigravity-plugin/skills/sinch-api-messages-send-card
Command: npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-messages-send-card-sinch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sending rich card messages (title, description, image, clickable buttons) over RCS requires constructing a correctly formatted card_message payload and authenticating against the Sinch Conversation API, which is tedious to do by hand. ## Core Features & Use Cases - Rich Card Delivery: Send a card with title, description, image URL, and optional choice buttons to any E.164 phone number. - MCP or Direct API Fallback: Uses the Sinch MCP tool when available, otherwise calls the Conversation API messages:send endpoint directly with OAuth2. - Use Case: A marketing team wants to send an RCS promotion with a product image and "Shop Now" and "Details" buttons to a customer; they provide the number, title, and choices and the message is sent immediately. ## Quick Start Ask the assistant to send an RCS card message to +14155551234 with title "Sale", description "50% off", and buttons "Shop Now" and "Details".

Frequently Asked Questions about sinch-api-messages-send-card

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send an RCS rich card message with Sinch?

Provide the recipient phone number in E.164 format, a card title, and optionally a description, image URL, and comma-separated button labels. The skill builds a card_message payload and posts it to the Sinch Conversation API messages:send endpoint.

What parameters does the Sinch card message API accept?

The card_message accepts a required title, plus optional description, media_message with an image URL, and a choices array where each choice has text and postback_data. The recipient is specified via channel_identities with the RCS channel.

Does Sinch card messaging work on channels other than RCS?

RCS is recommended for full card display with images and buttons. Other channels such as SMS may receive a transcoded text fallback version of the card instead of the rich layout.

Why does the Sinch card message fail with a configuration error?

The API call requires CONVERSATION_PROJECT_ID, CONVERSATION_KEY_ID, CONVERSATION_KEY_SECRET, CONVERSATION_REGION, and CONVERSATION_APP_ID environment variables. If these are missing and no MCP tool is available, the skill reports that the Sinch API is not configured.

Can I add clickable buttons to an RCS message?

Yes, pass comma-separated labels via the choices parameter. Each label becomes a choice with text and a postback_data value derived from the label, rendered as a clickable button on RCS.