List all organizations
Retrieves a comprehensive list of all organizations accessible to the authenticated user. This endpoint returns organization metadata including names, display names, and timestamps.
Authorization: Requires appropriate permissions to view organizations.
Rate Limiting: Standard rate limits apply.
Pagination: Supports offset-based pagination with limit and offset parameters.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Maximum number of items to return. Use -1 or omit to return all results. Valid values: -1 (all results) or 1–100.
-1 <= x <= 500Number of items to skip before starting to return results
x >= 0Response
List of organizations retrieved successfully
The unique identifier for the organization. Used as the resource name in API paths AND as the DNS subdomain label routing traffic to the org, so it follows RFC 1035 hostname rules — lowercase letters, digits, and hyphens; no underscores; no leading or trailing hyphen; max 63 chars.
1 - 63^[a-z0-9](?:[a-z0-9-]{0,61}[a-z0-9])?$Human-readable name for the organization, displayed in user interfaces
1 - 128^[^\u0000-\u001F\u007F]+$ISO 8601 timestamp indicating when the organization was created
ISO 8601 timestamp indicating when the organization was last modified
Version identifier of the Master Platform Agreement the organization
accepted at creation time (file basename, e.g. v1-2026-05-19).
Server-set: clients do not (and cannot) submit this field — when an
organization is created via the invite-redemption path, the server
stamps its current active MPA version. Null on legacy organizations
created before MPA acceptance was required.
Only the version is exposed on this resource. The per-user / per-
timestamp audit fields (mpa_accepted_by, mpa_accepted_at)
are kept internal — useful for compliance audit on the server
side, not for API consumers. If a future use case needs them on
the API, add them then; widening is easier than narrowing.
1 - 32^[a-zA-Z0-9._-]+$