sinch-conversation-api
Sinch Conversation API
Overview
One unified API to send and receive messages across SMS, WhatsApp, RCS, MMS, Viber Business, Facebook Messenger, Instagram, Telegram, KakaoTalk, LINE, and WeChat. The API transcodes between a generic message format and channel-specific formats automatically. This skill covers the API layer — apps, contacts, conversations, messages, webhooks, templates, and batch sending. Channel-specific guidance (sender IDs, encoding, templates, media limits) lives in the dedicated channel skills: sinch-sms, sinch-mms, sinch-rcs, sinch-whatsapp. Load only the skill(s) for the channel(s) the user is working with — never load a channel skill for a channel the task doesn't touch.
Agent Instructions
Before generating code, confirm two things with the user. Gather each as a separate, open-ended question — do not present a short multiple-choice list, because the user may want any supported language and either approach, and a short list anchors them to whatever you happened to enumerate.
- Approach — SDK or direct API (curl,
fetch,requests)? - Language — Only Node.js, Python, Java, or .NET when using an SDK. Any language or curl when using direct API.
Skip a question only when the answer is unambiguous from the user's own prompt or workspace:
- The user named it in this prompt or an earlier turn of this conversation.
- A Sinch dependency in the user's
package.json/requirements.txt/pyproject.toml/pom.xml/build.gradle/*.csproj— this fixes both approach (SDK) and language. - A bare project manifest with no Sinch dependency fixes only the language, not the approach.