iFood

Overview

For iFood, Session Start is an operational conversation mechanic. It should be used for marketplace-driven interactions such as order updates, support handling, delivery coordination, or other transactional events connected to the commerce flow. It is not a bulk-send mechanic and it should not be treated as a marketing channel.

The Sessions endpoint is still the entry point, but the contact identity and the operational context are defined by the iFood plugin contract installed in the tenant. In other words, the request shape remains familiar, but the identifier used in contactExternalID is usually a marketplace-specific identity rather than a regular phone number.

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:ifood:0",
    "pluginConnectionID": "<PLUGIN_CONNECTION_ID>",
    "contactExternalID": "<ORDER_CODE>",
    "messageKey": "text",
    "messageValue": "Your order is ready for pickup."
  }'

Channel-Specific Considerations

• contactExternalID should contain the orderCode from iFood order.
• messageValue usually contains the actual operational message that will be delivered through the marketplace conversation.
• sessionType and operatorID follow the common routing rules documented in the Session Start overview.
• Depending on the plugin implementation, Talqui may require additional contextual data related to the iFood operation. When that happens, use the exact payload contract defined for that plugin connection.

When to Use This Mechanic

Use iFood Session Start when your backend needs to trigger a message to a single marketplace contact as part of an operational flow already governed by the iFood channel. This is the correct choice for software-driven, transactional communication, not for campaign-style outreach.