Admin API

The Admin API allows you to programmatically manage your organization's resources, including organization members, workspaces, and API keys. This provides programmatic control over administrative tasks that would otherwise require manual configuration in the Claude Console.



Authentication

Authenticate with either credential. An Admin API key covers most endpoints; the service-account, federation-issuer, and federation-rule endpoints accept only an org:admin OAuth token. The following examples call the organization info endpoint both ways.



OAuth bearer token

Log in with the ant CLI under a dedicated profile, requesting the org:admin scope (see Admin access), then export the bearer token. A dedicated profile keeps your routine commands from running with elevated access:

ant auth login --profile admin --scope "org:admin"
export ANTHROPIC_OAUTH_TOKEN=$(ant auth print-credentials --profile admin --access-token)

Interactive tokens are short-lived; if requests start returning 401, re-run the export command, which refreshes the token automatically.

Call the Admin API with the exported token:

curl --fail-with-body -sS "https://api.anthropic.com/v1/organizations/me" \
  --header "anthropic-version: 2023-06-01" \
  --header "authorization: Bearer $ANTHROPIC_OAUTH_TOKEN"

An org:admin token grants access to the whole organization, regardless of the workspace the underlying profile or federation rule is bound to.

For CI and other non-interactive workloads, mint the token with Workload Identity Federation instead of logging in interactively. See Manage WIF with the Admin API.



Admin API key

To create an Admin API key for your organization type, see Create an Admin API key.

curl --fail-with-body -sS "https://api.anthropic.com/v1/organizations/me" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY"



How the Admin API works

When you use the Admin API:

1. You make requests using either credential from the Authentication section
2. The API allows you to manage:
   • Organization members and their roles
   • Organization member invites
   • Workspaces and their members
   • API keys
   • Service accounts, federation issuers, and federation rules (these endpoints require an org:admin OAuth token; Admin API keys are not accepted)

This is useful for:

• Automating user onboarding/offboarding
• Programmatically managing workspace access
• Monitoring and managing API key usage



Organization roles and permissions

There are five organization-level roles. See more details in the API Console roles and permissions article.

Organization owners and primary owners have all admin permissions and can additionally manage admins. All references to the admin role on this page also apply to owners and primary owners.



Key concepts



Organization members

You can list organization members, update member roles, and remove members.

# List organization members
curl "https://api.anthropic.com/v1/organizations/users?limit=10" \
  --header "anthropic-version: 2023-06-01" \
  --header "x-api-key: $ANTHROPIC_ADMIN_KEY"

# Update member role
curl "https://api.anthropic.com/v1/organizations/users/{user_id}" \
  --header "anthropic-version: 2023-06-01" \
  --header "content-type: application/json" \
  --header