List invitations
Lists invitations for this organization. Only owners signed in to the console can read them. Acceptance tokens and links are never returned.
oauth2 org:writeAuthorizationBearer <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:write
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 invitations.
application/json- response
items*array<>curl -X GET 'https://api.cloud.confidential.ai/v1/org/invitations' \ -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": "invitation_01E4ZCR3C56J083X43JQXF3JK5", "email": "alice@example.com", "role": "member", "state": "pending", "expiresAt": "2026-10-17T09:00:00Z" } ]}Delete your organization DELETE
Deletes the signed-in organization. This cannot be undone. Only an owner signed in to the console can call it. An organization is deleted only once it is empty: while it has an instance that is not `terminated`, a managed cluster, a load balancer, or a reservation that has not ended, been declined or been withdrawn, this returns `409 invalid_state` and deletes nothing, and `details.remaining` counts what is left. Delete or end those first. Once it is deleted nobody can sign in to the organization, its API keys stop working, and its members are no longer members of it. The usage up to then is invoiced as usual.
Invite a person POST
Sends a WorkOS invitation email for this organization and role. Only console owners can invite. A matching pending invitation is reused without sending another email.