siteId mandatory for Teams Public REST APIs and GraphQL teamSearchV2Until 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:
POST /org/{orgId}/teams/POST /org/{orgId}/teams/externalPOST /org/{orgId}/teams/{teamId}/external/linkGET /org/{orgId}/teamsteamSearchV2Customers have two paths to remain unblocked. Both are valid; Path A is faster, Path B is the recommended long-term direction.
siteIdThe 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 endpoint | GraphQL 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 query | Pass siteId on teamSearchV2. |
Rate this page: