sinch-conversation-api

Send and receive omnichannel messages via the Sinch Conversation API.

9|4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sinch/skills --skill sinch-conversation-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-conversation-api
Source: https://github.com/sinch/skills/tree/main/skills/sinch-conversation-api
Command: npx skills add https://github.com/sinch/skills --skill sinch-conversation-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Enable sending and receiving messages across many channels using one consistent API and reduce the complexity of building multi-channel messaging workflows, webhooks, templates, and batch campaigns.

Core Features & Use Cases

  • Omnichannel Delivery: Transcode and route messages for SMS, WhatsApp, RCS, MMS, Viber, Messenger, Instagram, Telegram, LINE, and WeChat with channel fallback.
  • Webhook & Event Handling: Prebuilt webhook trigger references, HMAC validation guidance, and test scripts for MESSAGE_INBOUND, MESSAGE_DELIVERY, CAPABILITY, and other triggers.
  • Templates & Batch Sending: Template management (V2) guidance and a Batch API reference for up to 1000 recipients plus per-recipient parameter substitution.
  • Developer Tools: Node.js scripts for sending messages, managing webhooks, running capability checks, and listing messages; includes guidance on region-specific base URLs, OAuth2 authentication, idempotency, and best practices.

Quick Start

Use the sinch-conversation-api skill to create an app, configure OAuth2 credentials and region, then run the provided Node.js send_sms script to send a test SMS to +15551234567.

Frequently Asked Questions about sinch-conversation-api

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

FAQPage Schema
How do I send omnichannel messages across SMS, WhatsApp, and RCS using one API?

To send omnichannel messages across SMS, WhatsApp, and RCS using one API, configure a Conversation API app with OAuth2 credentials and regional base URLs. The API transcodes and routes messages across ten channels with built-in channel fallback delivery behavior.

How do I validate webhook HMAC signatures for incoming message events?

To validate webhook HMAC signatures for incoming message events, apply the HMAC validation guidance provided for triggers like MESSAGE_INBOUND and MESSAGE_DELIVERY. This ensures your webhook endpoint securely verifies payloads received from the Conversation API.

Can I use batch sending to deliver personalized messages to up to 1000 recipients?

Yes, you can use batch sending to deliver personalized messages to up to 1000 recipients. The Batch API reference supports per-recipient parameter substitution, allowing you to customize message content for each user within a single bulk request.

Does the Sinch Conversation API support Node.js SDK usage for managing templates and contacts?

Yes, the Sinch Conversation API supports Node.js SDK usage for managing templates and contacts. It includes Node.js helper scripts for common operational tasks, alongside guidance on Template V2 management, capability checks, and direct-API integration.

What is the best way to manage regional base URLs and OAuth2 authentication for messaging workflows?

The best way to manage regional base URLs and OAuth2 authentication for messaging workflows is to configure them directly within your Conversation API app setup. The provided developer tools include best practices for handling region-specific routing and secure token authentication.

How do I track delivery and fallback behavior for Viber, Messenger, and Telegram messages?

To track delivery and fallback behavior for Viber, Messenger, and Telegram messages, implement prebuilt webhook trigger references for MESSAGE_DELIVERY events. This allows you to monitor message routing and automatic channel fallback performance across supported platforms.