Anthropic Administrator integrations and automation

The Anthropic Admin API is for the people who run a Claude API organization, not for calling models. It manages who belongs to the organization, which workspaces exist, who can use each workspace, and the status of API keys, and it reports usage and cost. Automating it typically means turning recurring admin chores into checks: a weekly list of keys nobody has used, a monthly cost breakdown per workspace, or an onboarding step that invites a new hire with the right role.

Authentication normally uses an Admin API key, which starts with sk-ant-admin and is different from an ordinary API key; an OAuth token with the org:admin scope also works. Only organization members with the admin role can provision an Admin API key, and the Admin API is unavailable for individual accounts; an organization has to be set up first. Treat this credential as highly privileged, since it can remove members and disable keys across every workspace.

The resources follow the organization structure. Users can be listed, have their role updated or be removed. Invites are created with an email and role, and expire after 21 days if not accepted. Workspaces can be created, renamed and archived, and workspace members carry their own workspace role. API keys can be listed, filtered by workspace or status, renamed, and set to inactive or archived; new API keys are created in the Console, not through the Admin API. The usage report returns token counts in time buckets that can be grouped by workspace, model or API key, and the cost report returns daily spend that can be grouped by workspace.

Because these calls change access, write disabling and removal as explicit rules with a list of exceptions, and have the workflow report what it would change before you let it act. Cost figures in the reports are the organization's own billing data, so they suit chargeback sheets where numbers must be exact.