Skip to main content

Claude Admin

Claude Admin lists members of a Claude organization and can remove a member, returning their purchased seat to the pool. It uses Anthropic's Admin API (GET/DELETE /v1/organizations/users).

The same endpoints cover:

  • Claude Enterprise (claude.ai) — company chat seats. This is usually what a customer means by “Claude members.”
  • Claude Console (platform.claude.com) — API / Console org members.

Create the Admin API key in the product you actually use. A key from one org cannot manage the other.

The API does not return or set seat tier. Invites consume a seat from the lowest tier with availability; removing a member returns that seat to the pool.

caution

Delete Org User cannot remove administrative roles (Console admin; Enterprise owner, membership_admin, primary_owner). If SCIM manages membership, delete returns 400. Scope this connector to administrators rather than All Users.

Authentication Types​

Claude Admin supports 1 authentication method:

  • Admin API key — sent in the x-api-key header.

Individual (non-organization) Claude accounts cannot use the Admin API.

Setting up an Admin API key​

Claude Enterprise (claude.ai)​

  1. Sign in as the parent organization's primary owner.
  2. Go to Organization settings → API.
  3. Create a key and select read:members and write:members.
  4. Copy the secret (sk-ant-api01-...) into Willow. It is shown only once.

Claude Console (platform.claude.com)​

  1. Sign in to Claude Console as an organization admin.
  2. Go to Settings → Admin keys.
  3. Click Create key, name it, choose an expiration, and click Create.
  4. Copy the secret (sk-ant-admin01-...) into Willow. It is shown only once.

Willow sends anthropic-version: 2023-06-01 on every request.

Available Tools​

  • List Org Users — GET /v1/organizations/users. Filter by email or role. Console roles: user, developer, billing, admin, claude_code_user. Enterprise roles: user, owner, primary_owner, membership_admin, managed. Page with after_id / before_id and limit (max 1000). No seat-tier field.
  • Delete Org User — DELETE /v1/organizations/users/{user_id}. Removes the member and returns their seat to the pool. Administrative roles cannot be deleted this way.

Troubleshooting​

401 or key rejected​

Cause: The secret is a regular inference key, or it was created in the other Claude product (Enterprise vs Console).

Solution: Create an Admin key in the same org you want to manage. Enterprise keys are created in claude.ai; Console keys in platform.claude.com.

403 missing scopes (Enterprise)​

Cause: The Enterprise key was created without read:members / write:members.

Solution: Create a new key with those scopes. Scopes are fixed at creation.

Cannot remove an admin / owner​

Cause: The Admin API refuses to delete administrative roles.

Solution: Change the member's role in the Claude UI first, or remove them there.

Empty list / unexpected org​

Cause: The key belongs to a different organization than the seats you expect.

Solution: Confirm whether the company uses Claude Enterprise, Claude Console, or both, and connect the matching key.

On this page