List your tenants

The tenants the signed-in user can act in, within the host's org.

GET /tenants

The tenants the signed-in user is a member of, in the org whose host you called. It is the list a tenant chooser shows, and exactly the set Switch tenant accepts.

These self-serve routes are scoped to the caller: the org comes from the host, the person from the token, and there is no org in the path. An org administrator manages every tenant through the Management API instead.

Authorization

Authorization: Bearer <access token>: a user token minted by the org whose host you call. A client_credentials token is refused with 401.

Response

200 with a JSON array. Not paginated.

[
  {
    "id": "tnt_…",
    "name": "Acme",
    "role": "owner",
    "logo": "https://…"
  }
]

Field	Type	Description
`id`	string	`tnt_…`
`name`	string
`logo`	URL
`role`	`owner` \| `admin` \| `member` \| `invited`	Your role in it. The same tenant reads `owner` to one person and `member` to another.

Which tenant the token is acting in is the token’s tnt claim; the list does not repeat it.

Errors

Status	`error`	When
`401`	`unauthorized`	No token, or an invalid, expired or ended one. See Authentication.

Example

curl https://acme.loginwith.dev/tenants \
  -H "Authorization: Bearer eyJ…"