Skip to main content
POST
Start headless account connection

Authorizations

Authorization
string
header
required

API key from Developer dashboard (Bearer token).

Headers

X-Profile-Id
integer

Act inside a profile (sub-account) you own: data reads and writes target the profile workspace while billing, rate limits and usage stay on your own account. Requires the profiles:manage scope. Returns 404 for profiles you do not own and 409 for paused profiles.

Path Parameters

platform
enum<string>
required

Platform to connect. All 15 platforms are supported (use twitter for X, gmb for Google Business). 14 are OAuth flows returning a connect_url (discord runs the server-webhook authorize flow). telegram is a CREDENTIAL connect instead: pass bot_token + chat in the body and the account connects immediately - no URL to open. whatsapp is a credential connect too: POST body { waba_id, phone_number_id, access_token } (a Meta system-user token) links one WhatsApp Business number.

Available options:
facebook,
instagram,
twitter,
linkedin,
youtube,
tiktok,
threads,
bluesky,
pinterest,
reddit,
snapchat,
tumblr,
gmb,
discord,
telegram,
whatsapp

Body

application/json
return_url
string<uri>

Optional URL to redirect the user to after they finish authorizing.

bot_token
string

Telegram only (required for it): your bot's token from @BotFather (e.g. 123456:AA...). Verified against Telegram (getMe/getChat/getChatMember - the bot must have posting rights in the chat) and stored encrypted.

chat
string

Telegram only (required for it): the target channel/group as @channelusername or a numeric chat id. Private chats are rejected.

identifier
string

Bluesky only: your handle (e.g. yourname.bsky.social), DID, or account email. Send it with app_password to connect without a browser.

app_password
string

Bluesky only: an app password generated in Bluesky settings (format xxxx-xxxx-xxxx-xxxx) - never your account password, which is rejected. Supplying this connects the account immediately instead of returning a connect_url.

waba_id
string

WhatsApp only (required for it): your WhatsApp Business Account id.

phone_number_id
string

WhatsApp only (required for it): the phone number id to connect, from the WABA.

access_token
string

WhatsApp only (required for it): a system-user access token with whatsapp_business_messaging and whatsapp_business_management. Stored encrypted.

Response

Connection link created. For telegram the response has no connect_url - the account is connected immediately and returned as {platform, account}.

success
enum<boolean>
Available options:
true
data
object
meta
object