WhatsApp Business

Overview

In WhatsApp Business integrations that allow outbound conversation opening without an approved model, Session Start is simpler than in WhatsApp API Official. The first outbound message is sent as a regular free-form message, so messageValue contains the exact text that will be delivered to the contact.

This is still a one-to-one mechanic. Your system calls the Sessions endpoint for one specific recipient, Talqui opens the session through the installed plugin connection, and the first outbound message becomes the first message of that session.

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": "urn:talqui:whatsapp-internal:0",
    "pluginConnectionID": "<PLUGIN_CONNECTION_ID>",
    "contactFullName": "<CONTACT_FULL_NAME>",
    "contactExternalID": "<PHONE_NUMBER>",
    "messageKey": "text",
    "messageValue": "Hello! Your order is ready for pickup."
  }'

How This Differs from WhatsApp API Official

• You usually send the actual outbound text directly in messageValue.
• You usually do not send campaignModelID.
• You usually do not send campaignVariables, unless your plugin contract explicitly requires them for some custom behavior.

Important Notes

• The common channel used in this mechanic is urn:talqui:whatsapp-internal:0.
• contactExternalID is usually the destination phone number in international format.
• If your tenant uses a custom plugin contract with additional required fields, include those fields exactly as defined for that plugin connection.

Use this mechanic when your integration needs to start a direct operational conversation on WhatsApp Business and the installed channel does not depend on an approved outbound model to open the session.