List your organizations
Lists every organization the signed-in person is a member of, with
their role in each, for the console's organization picker. Each
token acts in one of them, marked current; to act in another, sign
in again and pick it. Only people signed in to the console can list
them, and nothing but each org's ids, its name and the person's role
is returned.
oauth2 org:readAuthorizationBearer <token>A person's access token, sent as Authorization: Bearer <token>,
from the authorization code flow with PKCE (S256). A CLI on a
machine without a browser can use the device flow (RFC 8628) at
https://auth.confidential.ai/oauth2/device_authorization
instead. Ask for the resource https://api.cloud.confidential.ai
(RFC 8707): a token issued for any other resource, the MCP server's
included, is refused. A token acts for one person in one org, with
the scopes of the person's role there whatever the client asks for,
so ask the authorization server for none of the scopes below; they
are listed so that each operation can name the ones it needs.
Access tokens last minutes, and a refresh token is replaced at every
use.
Scope: org:read
Api-Version*stringThe API version the request is written against. This document
describes 2026-10-15. A missing header returns
400 api_version_required, and a version the API does not serve
returns 400 unsupported_api_version.
X-Correlation-ID?stringAn id of your own for this request, or for a group of requests, to
find them in our logs and yours. Logged with the request and returned
unchanged in X-Correlation-ID. The request id itself is always the
API's own, in X-Request-ID.
^[A-Za-z0-9._:-]+$1 <= length <= 128Org-Context?stringAdmin keys only: the id of the org to act in. Required with an admin
key, together with Access-Reason; with any other credential it
returns 400 invalid_request. Every request that carries it is
recorded in that org's operator-access log.
^org-[a-z0-9]([-a-z0-9]*[a-z0-9])?$5 <= length <= 63Access-Reason?stringAdmin keys only: why the operator is acting in the org, such as a
support ticket. Required with Org-Context. Recorded, verbatim, in
the org's operator-access log.
^[^\x00-\x1F\x7F]+$10 <= length <= 500List your organizations.
application/json- response
items*array<>curl -X GET 'https://api.cloud.confidential.ai/v1/orgs' \ -H 'Api-Version: 2026-10-15' \ -H 'X-Correlation-ID: rollout-2026-10-22' \ -H 'Access-Reason: Support ticket 4821: customer asked why i-6d3f9h2k8mzr failed'{ "items": [ { "id": "org-acme", "workosOrganizationId": "org_01M4HY1F2HB1F1V5NF26F81XBQ", "name": "Acme", "role": "owner", "current": true }, { "id": "org-k7m2q4x9w3np5r8t", "workosOrganizationId": "org_01M64AV6K2JR9PG5GAX8VC5QCF", "name": "Circles", "role": "member", "current": false } ]}List the org's audit events GET
Lists who changed what in the org, newest first: one event for each change an API call made, with the credential it came with, kept for as long as the org exists. A change's event is written in the same transaction as the change. `resource` lists the events of one resource, such as an instance's or a cluster's, including those from before it was deleted; its create is its oldest.
Get your organization GET
Returns the signed-in organization, the caller’s role and the active members copied from WorkOS. Member profiles come from WorkOS.