Skip to main content
POST
Add, promote or demote participants

Authorizations

x-api-key
string
header
required

Your workspace API key. Create one in Settings → API Keys; the plaintext value is shown once and never again.

Keys are scoped. A key needs conversations:send to send, conversations:read to read threads and messages, templates:read to list templates, and channels:read to list channels. A key missing the scope for an endpoint gets 403.

The CRM endpoints use the same resource:action form: leads:read, leads:create, leads:update, leads:delete, customers:read, customers:create, customers:update, customers:delete, customers:manage.

Several resources have no scope of their own and borrow one:

Grant only what the integration needs — a key that only sends notifications should hold conversations:send and nothing else.

X-Tenant-Id
string
header
required

Your workspace UUID. Required on every request in addition to x-api-key.

It does not select the workspace — data access is always scoped to the workspace that owns the API key, and a mismatched value cannot read anyone else's data.

Path Parameters

groupId
string
required

The provider's own group id — a Meta group id on the official provider, or the @g.us JID on the unofficial one (URL-encode it).

Body

application/json
channelId
string<uuid>
required
phoneNumbers
string[]
required

E.164 numbers without a plus.

action
enum<string>
default:add
Available options:
add,
promote,
demote

Response

Applied.