リファレンスHTTP APITeams

The teams the caller belongs to

GET
/v1/my-teams

Any signed-in person, as of this request: each team's id and name and the caller's role in it (lead or member), never who else is in it. By name, then id, limit per page (default 50, at most 100). Pass next_cursor back as cursor for the next page; it is null on the last one. A cursor that does not decode to a position in that order answers 400; a cursor only positions the read, so one from another workspace shows nothing of it. A team renamed while the pages are read can show twice or not at all; every other team shows once.

Auth: cookie session only; no scope.

Authorization

cookieSession
cookie__Host-werft_session<token>

For the web console: the browser session cookie set by POST /v1/auth/login. It holds the scopes of the user's workspace role (owner: all; admin and member: all but sessions:recover). Requests other than GET must also send X-Requested-With: werft-web.

Query Parameters

cursor?string

The next_cursor of the page before; omit it for the first page.

Length1 <= length
limit?integer

How many items a page holds at most.

Range1 <= value <= 100
Default50

Response Body

The caller's live teams, by name.

application/json
  1. response
items*array<>
next_cursor*|null
Example Request
curl -X GET 'https://example.com/v1/my-teams'
Example Response
{  "items": [    {      "id": "019a0000-0000-7000-8000-00000000b0a1",      "name": "research admins",      "role": "lead"    }  ],  "next_cursor": null}