Skip to main content
POST
Create messaging connector

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.

Body

application/json
platform
enum<string>
required
Available options:
telegram,
slack,
messenger,
teams,
discord,
gchat,
x,
whatsapp
name
string
required
Maximum string length: 120
assistant_id
string<uuid>
required
bot_token
string
bot_username
string
signing_secret
string
team_name
string
page_access_token
string
app_secret
string
verify_token
string
page_name
string
phone_number_id
string

WhatsApp Cloud API phone number ID

access_token
string

WhatsApp permanent System User token

waba_id
string

WhatsApp Business Account ID

display_phone_number
string
whatsapp_text_enabled
boolean
whatsapp_voice_enabled
boolean
whatsapp_outbound_voice_enabled
boolean
response_delay_sec
integer
Required range: 0 <= x <= 30
inactivity_timeout_min
integer
Required range: 1 <= x <= 1440
allow_retrigger
boolean
conversation_ended_webhook_url
string<uri> | null

Response

201 - application/json

Created connector (may include one-time webhook_secret for Telegram).

data
object