Create an Admin API key
Create an Admin API key for your Claude Console or Claude Enterprise organization.
An Admin API key authenticates calls to the APIs that manage and report on your organization, such as the Admin API and the Compliance API. One key can work with several of these APIs.
Which key do you need?
The key you need depends on which Claude product your organization uses: Claude Console (Claude Platform) or Claude Enterprise.
| Organization | Claude Console | Claude Enterprise |
|---|---|---|
| Sign-in address | platform.claude.com | claude.ai |
| Where to create it | Admin keys page in the Claude Console | claude.ai > Organization settings > API |
| Key prefix | sk-ant-admin01-... | sk-ant-api01-... |
| Who can create it | Organization members with the admin role | Primary owner: any scope Organization owner: Compliance API scopes only, for their own organization |
| Scopes | None to select: every key has full access to the endpoints that accept it | Choose scopes when you create the key. The key works only with the APIs your scopes cover |
| Works with | Admin API Usage and Cost Analytics API Compliance API Activity Feed Usage and Cost API (legacy) Rate Limits API Claude Code Analytics API | Admin API user management Usage and Cost Analytics API Compliance API Claude Enterprise Analytics API Plugins API Claude Tag API Spend Limits API |
Most keys reach only the organization you created them in. Some keys, such as those with Compliance API, group, or audit scopes, can reach further if your company links its organizations under a parent organization. If your company uses both Claude Console and Claude Enterprise, create one key in each.
Create a key for a Claude Console organization
An individual Claude Console account cannot create this key, so set up an organization first. To use the key with the Activity Feed, enable the Compliance API before you create it.
Open Admin keys settings
Sign in to the Claude Console as an organization admin. Go to the Admin keys page (
platform.claude.com/settings/admin-keys).Create the key
Click Create admin key, give it a name, select a key expiration, and click Add.
Copy and store the secret
Copy the displayed secret (starting with
sk-ant-admin01-) and store it in your secrets manager. The full secret is shown only once.
Create a key for a Claude Enterprise organization
Open API settings
Sign in to claude.ai as the primary owner or an organization owner. Go to claude.ai > Organization settings > API and find the Keys section.
Create the key
Click Create key, name the key, and select the scopes you need from the scopes table. The primary owner can combine scopes from different APIs (for example,
read:analyticsandread:spend_limits) on a single key.If the Key access options appear when you select a Compliance API scope, Only this organization is selected by default. To reach every organization under your parent organization, choose All organizations. Such a key can hold only Compliance API, group, and audit scopes.
Click Create. If the key has the
delete:compliance_user_datascope, also click Confirm and create key.Copy and store the secret
Copy the displayed secret (starting with
sk-ant-api01-) and store it in your secrets manager. The full secret is shown only once.
Choose scopes for a Claude Enterprise key
When you create a Claude Enterprise key, select every scope that the APIs you plan to call require. Scopes are fixed at creation; to add a scope later, create a new key. A key that holds only Compliance API scopes is also called a Compliance Access Key. A key that holds only read:analytics is also called an Analytics API key.
| To call... | Select these scopes |
|---|---|
| Admin API user management: list and look up members and invites; read custom roles and their permissions | read:members |
Admin API user management: change member roles, remove members, sign members out everywhere (beta), and create and withdraw invites (to assign the managed role on a role change or an invite, also select write:rbac_groups) | write:members |
| Admin API user management: read groups and their members | read:rbac_groups |
Admin API user management: create, rename, and delete groups; add and remove group members; with write:members, assign the managed role (on an invite or a role change) or assign groups on an invite | write:rbac_groups |
| Plugins API: read plugins, versions, installation settings, shares, and marketplaces; download plugin files, including the files of members’ personal plugins; validate a marketplace before you connect it | read:plugins |
Plugins API: upload plugins and versions; choose which version members are served; delete plugins, including members’ personal plugins; set and remove installation settings; set a marketplace’s default installation setting; validate a marketplace before you connect it (to read plugins, also select read:plugins) | write:plugins |
| Claude Tag API: read Claude Tag’s settings on Slack channels and Slack workspaces; list Access bundles and where they are attached (no other scope grants read access to the Claude Tag API) | read:claude_tag |
Claude Tag API: set up and remove channels; change settings; attach and detach Access bundles (to read as well, also select read:claude_tag) | write:claude_tag |
| Spend Limits API: read members’ effective spend limits and increase requests | read:spend_limits |
| Spend Limits API: set or clear per-user spend limits; approve or deny increase requests | write:spend_limits |
| Claude Enterprise Analytics API: engagement, adoption, cost, and usage reports; Usage and Cost Analytics API: token usage and cost reports | read:analytics |
| Compliance API Activity Feed: organization-wide activity events | read:compliance_activities |
Compliance API chat, file, and project endpoints and Compliance API session endpoints: read chats, files, projects, session transcripts, and organization users; together with read:compliance_org_data, also who made a Security posture attestation, where the endpoint returns it: a user ID | read:compliance_user_data |
| Compliance API chat, file, and project endpoints: delete chats, files, and projects | delete:compliance_user_data |
Compliance API organization endpoints: read organization metadata and effective settings, and an organization’s Security posture; Plugins API: every GET endpoint, including file downloads | read:compliance_org_data |
Admin API user management read endpoints, every Compliance API read endpoint, and every Plugins API GET endpoint, including file downloads, with a single read-only scope (for security-audit integrations; does not include the Spend Limits or Analytics APIs) | read:org_audit |
Compliance API scopes need the Compliance API enabled before you can create a key with them. The read:analytics scope needs access to the Claude Enterprise Analytics API.
The read:plugins and write:plugins scopes need an organization that can use the Plugins API, and they act only on the organization you created the key in. Keys with read:org_audit or read:compliance_org_data can read the Plugins API only in organizations that can use it. See Plugins API scopes. To read another organization’s plugins, see Reading another organization under the same parent.
Use the key
Pass the key in the x-api-key header on every request. See each API’s documentation for complete request examples.
A call to an endpoint outside the key’s scopes returns 403 Forbidden. The error message names the scopes the endpoint accepts.
Neither a Claude Console key nor a Claude Enterprise key works with the Admin API’s service-account, federation-issuer, or federation-rule endpoints. Those endpoints accept only an OAuth bearer token with the org:admin scope. See OAuth bearer token.
Next steps
Manage organization members, workspaces, and API keys.
Set per-member spend limits and review increase requests for your Claude Enterprise organization.
Report on Claude Code productivity or Claude Enterprise engagement and adoption.
Audit activity and retrieve or delete user content across your organization.
Was this page helpful?