API Reference
Provider Guide

Unified message sending support

Message payloads mapped by the current POST /v1/messages adapters. Provider rollout and upstream availability can still vary by account and region.

Capability

CapabilityTelegramWhatsAppXLINEZaloTikTok
textFullFullFullFullFullFull
imageFullFullFullFullFullFull
videoFullFullFullFullFullFull
audioFullFullPartialFullFullNot supported
documentFullFullFullFullFullNot supported
fileFullFullFullFullFullNot supported
contactNot supportedFullNot supportedNot supportedNot supportedNot supported
reply_to.reply_tokenNot supportedFullNot supportedNot supportedNot supportedNot supported
mentionsNot supportedFullNot supportedPartialNot supportedNot supported
provider_data.parse_modeFullNot supportedNot supportedNot supportedNot supportedNot supported

Notes

  • WhatsApp audio messages take content as a JSON string {"url":"...","seconds":N,"waveform":"..."} — only url is mandatory.
  • parse_mode (Markdown / HTML) is fully honored by Telegram. Other providers ignore the field today.
  • X accepts audio only as part of a media attachment, not as a standalone voice note.
  • X sends document payloads as media attachments; upstream file type and size limits still apply.
  • reply_to.reply_token sends a quoted reply: pass data.message.reply_token from the inbound event back unchanged. WhatsApp only for now — other providers return 501 unsupported_by_provider; a tampered token returns 400 invalid_reply_token.
  • mentions tags group members: declare ids in the mentions array and place {{@<id>}} anchors in text / caption. WhatsApp supports text and media captions; LINE currently supports text only. Other providers ignore the field. provider_data.mentions is deprecated.
  • TikTok image and video messages accept only url or file_url; caption and mentions are not supported.