Chelabase
ManagementTeams

Create a team

POST
/v1/teams

An empty team: no members, no grants. One team_created access event.

Authorization

bearer
AuthorizationBearer <token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

description?string

At most 500 characters. Default empty.

name*string

Trimmed; 1 to 80 characters, unique in the tenant ignoring case.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/teams" \  -H "Content-Type: application/json" \  -d '{    "name": "string"  }'
{  "created_at": "2019-08-24T14:15:22Z",  "description": "string",  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",  "member_count": 0,  "member_ids": [    "6059d331-91d8-43de-a6af-f1a743933a5b"  ],  "name": "string",  "projects": [    {      "pg_roles": [        "string"      ],      "platform_role": "viewer",      "project_id": "405d8375-3514-403b-8c43-83ae74cfe0e9"    }  ],  "updated_at": "2019-08-24T14:15:22Z"}

List the tenant's teams GET

Every team of the tenant, by name ignoring case, with its member count and its grants on the projects the caller can see (a tenant admin sees all; anyone else the projects where they have any access). A team's Postgres roles on a project are shown only to tenant admins and to Admins of that project; others get `pg_roles: null`. No member ids (`getTeam` has them).

Read a team GET

The team with its member ids, filtered as `listTeams` is.