Exchange API-key client credentials for an access token

Uses HTTP Basic authentication where the API key ID is the client ID and the one-time ck_ token is the client secret. Requested scopes must be a subset of the API key scope ceiling.

POST /oauth/token

Exchange API-key client credentials for an access token

cURL

curl --request POST \
  --url https://app.communicate.so/api/v1/oauth/token \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data grant_type=client_credentials

200

{
  "access_token": "<string>",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "<string>"
}

Body

application/x-www-form-urlencoded

grant_type · enum<string> · required

Available options: client_credentials

scope · string

Space-delimited subset of agents:read and chat:write.

resource · enum<string> · default: https://app.communicate.so/api/v1

RFC 8707 resource audience. MCP tokens accept only agents:read.

Available options: https://app.communicate.so/api/v1, https://app.communicate.so/mcp

Response

200

application/json

Short-lived scoped bearer token

access_token · string · required

token_type · enum<string> · required

Available options: Bearer

expires_in · integer · required

scope · string · required