Developer
News and Updates
Get Support
Sign in
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Last updated Sep 15, 2026

We're making siteId mandatory for Teams Public REST APIs and GraphQL teamSearchV2

Until now, the siteId parameter was optional on a set of Teams public APIs. From now onwards, the same siteId parameter becomes mandatory. Any request that does not provide a siteId will be rejected with a 400 Bad Request response.

Following APIs now require mandatory siteId:

  • Create Team - POST /org/{orgId}/teams/
  • Create external team - POST /org/{orgId}/teams/external
  • Link external team - POST /org/{orgId}/teams/{teamId}/external/link
  • List teams - GET /org/{orgId}/teams
  • GraphQL query - teamSearchV2

What you need to do?

Customers have two paths to remain unblocked. Both are valid; Path A is faster, Path B is the recommended long-term direction.

Path A: Start passing siteId

The simplest fix. Works for all the affected APIs. The customer adds a valid siteId (their cloudId) to every request to these endpoints. No other changes are required.

The Teams GraphQL API is the long-term shape we want customers to move to. The following equivalents are available today:

REST endpointGraphQL alternative
POST /org/{orgId}/teams/ (Create team)createTeam mutation
POST /org/{orgId}/teams/external (Create external team)createExternalTeam mutation
POST /org/{orgId}/teams/{teamId}/external/link (Link external team)linkExternalTeam mutation
GET /org/{orgId}/teams (List teams)No GraphQL alternative today. Passing siteId to the API is the only option.
teamSearchV2 GraphQL queryPass siteId on teamSearchV2.

Rate this page: