Anthropic
Visualize Anthropic organization data in the JupiterOne graph. Map users to workspaces, track API key ownership and status, and monitor identity and access changes through custom queries and alerts.
- Installation
- Authorization
- Data Model
- Types
- Release Notes
Installation
The Anthropic integration ingests organization details, users, workspaces, workspace memberships, and API keys using the Anthropic Admin API. Before setting up the integration in JupiterOne, you will need to create an Admin API key in the Claude Console.
Prerequisites
- An Anthropic organization (the Admin API is unavailable for individual accounts). If you have not set one up, go to Console > Settings > Organization first.
- An organization member with the admin role — only admins can create Admin API keys.
- Access to JupiterOne with permission to configure integrations.
Creating an Admin API key in Anthropic
- Log in to the Claude Console as an organization admin.
- Navigate to Settings > Admin Keys (https://platform.claude.com/settings/admin-keys).
- Click Create Admin Key and give it a recognizable name (for example,
JupiterOne Integration). - Copy the generated key — it starts with
sk-ant-adminand is shown only once.
Admin API keys are separate from standard API keys. Only organization admins can create them, and they provide access to the organization management endpoints (/v1/organizations/me, /v1/organizations/users, /v1/organizations/workspaces, workspace members, and /v1/organizations/api_keys). No additional scope configuration is required — the integration only reads from these endpoints.
Configuration in JupiterOne
To install the Anthropic integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Anthropic. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Anthropic account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
Your Anthropic API Key — the Admin API key created above (starts with
sk-ant-admin). This field is required. -
Optionally, a Base URL to override the Anthropic API endpoint. Leave blank to use the default
https://api.anthropic.com. -
Optionally, an Anthropic Version to override the
anthropic-versionrequest header. Leave blank to use the default2023-06-01.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Roles
RBAC roles that must be assigned to the integration principal.
Show Roles (1)
admin
Documentation Links
Links to provider documentation relevant to setup and configuration.
Show Documentation Links (1)
Per-Step Breakdown
Detailed authorization requirements for each ingestion step.
Show all steps (4)
| Step | Roles |
|---|---|
| Fetch Api Keys | admin |
| Fetch Users | admin |
| Fetch Workspace Members | admin |
| Fetch Workspaces | admin |
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Account | anthropic_account | Account |
| Api Key | anthropic_api_key | AccessKey |
| User | anthropic_user | User |
| Workspace | anthropic_workspace | Group |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
anthropic_account | HAS | anthropic_user |
anthropic_account | HAS | anthropic_workspace |
anthropic_user | ASSIGNED | anthropic_workspace |
anthropic_user | CREATED | anthropic_api_key |
anthropic_workspace | HAS | anthropic_api_key |
Anthropic Account
anthropic_account inherits from Account
Anthropic Api Key
anthropic_api_key inherits from AccessKey
| Property | Type | Description | Specifications |
|---|---|---|---|
partialKeyHint | string | A partial hint of the API key value | |
status | string | The status of the API key (active, inactive, archived) |
Anthropic User
anthropic_user inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
email | array of strings | The email address(es) of the user | |
role | string | The role of the user in the organization (user, developer, billing, admin, claude_code_user, managed) |
Anthropic Workspace
anthropic_workspace inherits from Group
| Property | Type | Description | Specifications |
|---|---|---|---|
archivedOn | number | Timestamp when the workspace was archived | |
displayColor | string | The display color of the workspace |