Single sign-on

List the people linked through single sign-on

The people linked to the workspace's provider: username, subject (their id at the provider), email (as the provider gave it, for showing), linked_at and last_used_at.

GET/workspaces/{workspace}/sso/identities

Owners only, as people.

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

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s name, e.g. “acme”.

Example request

curl https://api.g1t.sh/workspaces/flagon-io/sso/identities \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

[
  {
    "username": "syntaqx",
    "subject": "chase@flagon.io",
    "email": "chase@flagon.io",
    "linked_at": "2026-10-17T09:12:44.000Z",
    "last_used_at": "2026-10-17T14:02:31.000Z"
  }
]

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 a token without the scope it needs.
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.