List a workspace's members

A workspace's members, owners first, then by username.

GET/workspaces/{workspace}/members

Each has their username, display_username (the username as they wrote it), name, avatar, role (owner or member), the roles they hold besides it (org_roles: billing_manager, security_manager), and, when an owner asks, whether they have two-factor authentication on (two_factor; null for anyone else). Members only.

Owners first, then by username. two_factor is shown to owners only, and is null for anyone else. 403 for anyone who is not a member. See Workspaces.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workspace with action list_members, and the same inputs
Scope: An access token needs workspace:read.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s slug, e.g. “flagon-io”.

Example request

curl https://api.g1t.sh/workspaces/acme-labs/members \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

[
  {
    "username": "ada",
    "display_username": "Ada",
    "role": "owner",
    "org_roles": [],
    "two_factor": true,
    "name": "Ada Lovelace",
    "avatar": null
  },
  {
    "username": "grace",
    "display_username": "grace",
    "role": "member",
    "org_roles": [
      "security_manager"
    ],
    "two_factor": false,
    "name": "Grace Hopper",
    "avatar": null
  }
]

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
422	`invalid`	The input is not valid. `message` says which field and why.