Team - Exo

What this family does

GET /v1/team returns the calling key’s organization and a count of its human members. GET /v1/team/members enumerates those members. Provisioned subjects and sandbox identities are never counted or listed. They are partitions, not people, and their internal ids are an isolation detail.

Routes

Method	Path	Scope	What it does
`GET`	`/v1/team`	`read`	Get the organization
`GET`	`/v1/team/members`	`admin`	List organization members

The shape of a call

Read the organization.

curl https://api.get-exo.com/v1/team \
  -H "X-Exo-API-Key: $EXO_KEY"

import httpx

response = httpx.get(
    "https://api.get-exo.com/v1/team",
    headers={"X-Exo-API-Key": EXO_KEY},
)

const response = await fetch("https://api.get-exo.com/v1/team", {
  headers: { "X-Exo-API-Key": process.env.EXO_KEY! },
});

The response:

{
  "id": "0d5b7c92-3a41-4e88-9b02-6f7c1d4a5e30",
  "name": "Acme",
  "slug": "acme",
  "memberCount": 4,
  "createdAt": "2026-05-02T11:41:00Z"
}

Traps

Listing members requires admin. It enumerates real people with their email and role, so it follows the same posture as the organization-wide usage view.

API reference

Base URL, authentication, and the conventions every route shares.

Errors

The problem envelope and the full code catalogue.

Download an export document

Get the organization

⌘I

​What this family does

​Routes

​The shape of a call

​Traps

​Related