Skip to main content
POST
Create a team

Authorizations

Authorization
string
header
required

The id_token from POST /auth/v1/signin, sent as Authorization: Bearer <id_token>. Not the access_token — that one does not carry the identity Cloud Chat authorizes on.

Headers

cloudchat-instance
integer
required

Your Cloud Chat instance ID — an integer, fixed for your company, told at onboarding. The API overview explains how instances work, how to find yours, and the errors a wrong or missing value produces.

Example:

1

Path Parameters

accountId
integer
required

Your Cloud Chat account. It has to be an account your token grants membership on, and it has to live on the instance in the cloudchat-instance header — the two travel together. Account numbers are only unique within an instance, so the same number is a different company on another instance. Usually a mismatched pair fails closed with a 401, because your user does not exist on the other instance — but if your identity happens to exist on both, the call succeeds against the other company's data, silently. Read it and you are looking at the wrong help center; write it and you have stored into the wrong account. Send the two values that were given to you together, and never try a number to see what answers.

Example:

1

Body

application/json

The team goes under a team wrapper. Administrator only.

team
object
required

Response

Created.

A team of the account.

id
integer
required
Example:

5

name
string
required
Example:

"billing"

description
string | null
required
Example:

"Billing and invoicing questions."

allow_auto_assign
boolean | null
required
Example:

true

working_hours_enabled
boolean
required
Example:

false

out_of_office_message
string | null
required
Example:

null

timezone
string | null
required
Example:

"America/Sao_Paulo"

system_managed
boolean
required

true for a team provisioned by the platform itself. It can be read like any other team but update always answers 403 on it.

Example:

false

created_at
string<date-time>
required
Example:

"2026-05-02T11:04:17.000Z"

updated_at
string<date-time>
required
Example:

"2026-08-10T14:32:05.123Z"