Who this is for: Organization owners and the security or compliance teams who connect Claude for Government to their agency’s log management or SIEM platform.
The Compliance API is a read-only HTTP endpoint that lets your security tools pull a continuous feed of audit events covering administrative activity across your organization, such as sign-ins, role changes, key creations, and seat assignments. A scheduled job can poll the endpoint and forward each event to a SIEM such as Splunk or Microsoft Sentinel.
The API is available to every Claude for Government organization by default, and it is read-only, so a compromised key cannot change anything in your organization.
Managing API keys
Open Compliance API in the organization admin portal to create and manage keys. The page lists every key that has been issued for your organization, showing its name, a hint with the last few characters of the key so you can tell them apart, when it was created, and whether it is active or revoked.
To create a key, enter a name and click Create key. The full value is shown once, immediately after creation. Copy it somewhere safe before clicking Done.
The full key value is shown only once, at creation time. If you lose it, create a new key and revoke the old one.
Calling the API
Send a GET request to /v1/compliance/activities on the Claude for Government host provided to you during onboarding, with your key in the x-api-key header.
Query parameters
| Parameter | Description |
|---|
since or created_at.gte | The earliest event time to return, as an RFC 3339 timestamp or epoch seconds. A lower bound is required on every request that does not carry a cursor. |
until or created_at.lte | The latest event time to return, in the same format. Optional. |
after_id | An opaque cursor that continues from where a previous page left off. Pass the last_id value from the previous response. |
before_id | An opaque cursor that pages in the other direction. Pass the first_id value from the previous response. Cannot be combined with after_id. |
actor_ids[] | Return only events performed by the listed actors. Repeat the parameter to pass more than one. |
activity_types[] | Return only events of the listed types. Repeat the parameter to pass more than one. |
limit | Maximum events per page, from 1 to 5000. Defaults to 100. |
created_at.gt and created_at.lt are also accepted if your collector needs them.
The response is a JSON envelope containing a page of events and the cursors for the next and previous pages.
The actor object identifies who performed the action. Its type is one of:
user_actor for a person acting through the product or admin portal.admin_api_key_actor for an action taken through an administrative API key.anthropic_actor for an action performed by Anthropic personnel or systems on your behalf, such as initial provisioning. No individual identity is included.
Each event also carries fields specific to its type, such as the role a user was changed to or the name of a key that was created.
Activity types
Event types use a dotted resource.action naming convention. The categories emitted today include:
- Users such as
user.created, user.signed_in, user.role_changed, user.deactivated, and user.reactivated.
- Organizations such as
org.created, org.renamed, and org.deactivated.
- Credentials such as
api_key.created, scim_token.created, and scim_token.revoked.
- Seats and tiers such as
seat_allocation.set, seat_allocation.tier_assigned, seat_tier.created, and seat_tier.updated.
- Configuration such as
org_config.capabilities_set.
New types may be added over time, so a collector should forward unfamiliar types rather than reject them.
Connecting to your SIEM
Most deployments run a small scheduled worker that polls the API on a fixed interval, forwards each event to the SIEM’s HTTP ingest endpoint, and records a time watermark so the next run picks up where the last one left off.
A typical run requests since=<watermark>, forwards every event returned, and if has_more is true, follows after_id=<last_id> for each further page until has_more is false. After all pages are drained, advance your watermark to the newest created_at you saw. Event id values are stable and unique, so your collector can deduplicate on id and safely retry a page or use an overlapping since without creating duplicate records in the SIEM.
When the API is disabled
Your tenant administrator can turn off the Compliance API enabled setting on the tenant Config page. When that setting is off, the Create key button is hidden in the portal, and every call to /v1/compliance/activities returns a 400 error, including calls made with keys that were valid before the setting changed.
Listing and revoking existing keys in the portal remains available even when the setting is off, so an exposed key can still be revoked.
Things to know
- The Compliance API returns governance and audit events only. It does not return conversation content, files, or anything your users type into Claude.
- Each organization can hold up to 50 active keys at once. Revoked keys do not count toward this limit.
- Events are returned newest first within each page.
first_id and last_id are opaque cursors. Pass them back exactly as received rather than constructing them yourself.- If your network enforces a tenant restriction, the same restriction applies to Compliance API requests.
