Skip to main content
GET
Get the organization
Read scope: this is the caller’s own org, and the fields (display name, slug) are the same ones GET /v1/me already returns. memberCount counts humans only — provisioned subjects (role='service') are not team members. To enumerate the members themselves, use GET /v1/team/members, which requires admin scope.

Authorization

This route requires the read scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Response

Successful Response

The calling key's organization (spec 4.12).

memberCount counts HUMAN members only: rows with role='service' (provisioned subjects and sandbox identities) are excluded, so a solo developer org with 10,000 subjects still reports memberCount: 1.

createdAt
string<date-time>
required
id
string
required
memberCount
integer
required
name
string | null
slug
string | null