Skip to main content
POST
Account Connect
Connects a WhatsApp Business Account (WABA) to ChatSyncs programmatically — a POST request since it creates/updates a connection, and because access_token is sensitive and shouldn’t be sent as a GET query parameter.
Where to find user_id: call Get My Info first — copy the user_id value from its response and use that here.
Where to find whatsapp_business_account_id: since this endpoint is what connects the WABA to ChatSyncs in the first place, it won’t show up in ChatSyncs’s own Connect Account page yet — get it from Meta instead. See Meta Developer Account Setup for a first-time setup, or Finding Your IDs & API Token for where it lives once a different WABA is already connected.
Where to find access_token: this must be a permanent system-user token, not the temporary token Meta’s API Setup screen shows by default — a temporary token expires in about an hour and the connection will silently break. See Access Tokens (Temporary vs Permanent) to generate a permanent one.

Body

application/x-www-form-urlencoded
apiToken
string
required

Your ChatSyncs API key (not a WhatsApp/Meta access token). Where to find it.

Example:

"API-KEY"

user_id
integer
required

The ChatSyncs user ID of the account owner. Get this from Get My Info.

Example:

123

whatsapp_business_account_id
string
required

The WhatsApp Business Account ID from Meta. Where to find it.

Example:

"WHATSAPP-BUSINESS-ACCOUNT-ID"

access_token
string
required

A permanent Meta system-user access token for the WhatsApp Business Account -- not the temporary token, which expires in ~1 hour. See Access Tokens (Temporary vs Permanent) to generate one.

Example:

"PERMANENT-ACCESS-TOKEN"

Response

200 - application/json

Standard ChatSyncs response. status is "1" on success and "0" on failure.

status
string

"1" = success, "0" = failure.

message
string

Human-readable result message.