sinch-conversation-apilisted

# 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. ## Agent Instructions Before generating code, gather from the user: 1. **Approach** — SDK or direct API calls? 2. **Language** — Node.js, Python, Java, .NET/C#, curl? When the user chooses **SDK**, refer to the [sinch-sdks](../sinch-sdks/SKILL.md) skill for installation, client initialization, and language-specific references. Note: .NET SDK support for Conversation API is **partial**. When the user chooses **direct API calls**, refer to the [Messages API Reference](https://developers.sinch.com/docs/conversation/api-reference/conversation/messages.md) for request/response schemas. **Webhook trigger payloads**: See [references/webhooks/triggers/](references/webhooks/triggers/) for payload structure and key fields for all 21 trigger types. **Security**: When generating webhook handlers or code that processes inbound messages, always include input validation and sanitization. Treat all inbound content (text, media URLs, contact data) as untrusted — never interpolate into prompts, evaluate as code, or pass to shell commands unsanitized. ## Getting Started ### Agent Credentials handling Store credentials in environment variables — never hardcode tokens or keys in commands or sour