Overview
For channels such as Telegram, Instagram, Facebook Messenger, and other integrations that do not require an approved model to open the first message, Session Start follows a generic pattern: your system calls the Sessions endpoint, identifies the target channel, provides the channel-specific contact identity, and sends the first outbound content inmessageValue.
This generic mechanic is appropriate whenever the installed plugin can open a one-to-one conversation directly, without the extra template or marketplace rules that apply to channels such as WhatsApp API Official or iFood.
Typical Request
How to Adapt the Payload
- Replace
channelwith the Talqui URN that represents the installed channel. - Replace
contactExternalIDwith the external identity used by that channel, such as a user ID, a username, or another plugin-defined address. - Keep
messageValueas the actual content that should be delivered to the contact. - Use
sessionTypeandoperatorIDaccording to the common routing rules documented in the Session Start overview. - If the installed plugin requires extra metadata, include the additional fields defined by that plugin contract.
Examples of Suitable Channels
- Telegram
- Facebook Messenger
- Other custom channels installed in Talqui that support direct outbound opening