Generic Channels

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 in messageValue.

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

curl --request POST \
  --url https://api.talqui.chat/tenants/<TENANT_ID>/sessions \
  --header 'Authorization: PluginConnection <PLUGIN_CONNECTION_TOKEN>' \
  --header 'content-type: application/json' \
  --data '{
    "channel": "<CHANNEL_URN>",
    "pluginConnectionID": "<PLUGIN_CONNECTION_ID>",
    "contactFullName": "<CONTACT_FULL_NAME>",
    "contactExternalID": "<CHANNEL_SPECIFIC_CONTACT_ID>",
    "messageKey": "text",
    "messageValue": "Hello! This conversation was started by an external system."
  }'

How to Adapt the Payload

• Replace channel with the Talqui URN that represents the installed channel.
• Replace contactExternalID with the external identity used by that channel, such as a user ID, a username, or another plugin-defined address.
• Keep messageValue as the actual content that should be delivered to the contact.
• If the installed plugin requires extra metadata, include the additional fields defined by that plugin contract.

Examples of Suitable Channels

• Telegram
• Instagram
• Facebook Messenger
• Other custom channels installed in Talqui that support direct outbound opening

Use this pattern as the baseline Session Start mechanic whenever the channel does not depend on approved outbound models and does not require a marketplace-specific operational context.