List the org's teams
Teams of the caller's active org, ordered by key. Never empty for a used workspace — the first request bootstraps a "General" (GEN) team.
View as MarkdownAuthorization
bearer In: header
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/teams"{ "teams": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "key": "string", "name": "string", "created": "2019-08-24T14:15:22Z" } ]}List the org's members
Members of the caller's active org (upserted from JWTs on each request), ordered by name then email — used for assignee and lead pickers.
Create a team
Creates a team in the caller's org, seeded with the default workflow states (Backlog, Todo, In Progress, Done, Canceled) so it can hold issues immediately. Key and name are stored trimmed, and both are unique per WORKSPACE — not per team like the names below, since teams are the tenant root. A key or a name another team in the org already holds is a 409. The two comparisons differ: names are compared trimmed and case-insensitively (one workspace cannot hold "Design" and "design", though two workspaces may each hold their own), while the key comparison is exact, so "eng" and "ENG" are currently two different keys in one workspace.