---
title: "Get a Claude Compliance integration account"
method: GET
path: "/api/v2/integration-interfaces/claude-compliance/accounts/{account_id}"
tags: ["Claude Compliance Integration"]
---

# Get a Claude Compliance integration account

`GET /api/v2/integration-interfaces/claude-compliance/accounts/{account_id}`

## Request

- Base URL: `https://api.datadoghq.com`
- URL: `https://api.datadoghq.com/api/v2/integration-interfaces/claude-compliance/accounts/{account_id}`
- Auth: one of:
  - API key in header `DD-API-KEY` and API key in header `DD-APPLICATION-KEY`
  - OAuth 2
    - Authorization code: `/oauth2/v1/authorize`
    - Token URL: `/oauth2/v1/token`

Get a Claude Compliance integration account.

## Path parameters

- `account_id` string, required

## Response `200`

OK

- ClaudeComplianceIntegrationAccountResponse: Response payload for a single Claude Compliance integration account.
  - `data` ClaudeComplianceIntegrationAccountResponseData, required: Data envelope of a Claude Compliance integration account, including server-assigned identity.
    - `attributes` ClaudeComplianceIntegrationAccountResponseAttributes, required: Attributes of a Claude Compliance integration account returned in responses.
      - `authentication` ClaudeComplianceIntegrationAccountAuthenticationResponse: The bearer token authentication method configured on the account.
        - `auth_type` 'bearer_token', required: The authentication method type.
      - `dataflows` ClaudeComplianceIntegrationDataflowsResponse: Data Datadog collects from Claude Compliance, keyed by dataflow ID.
        - `anthropic-compliance-logs` ClaudeComplianceComplianceLogsIntegrationDataflowResponse: Audit activity logs from the Anthropic Compliance API, such as SSO sign-ins, API key lifecycle events, member and role changes, and Claude chat and file access. [Cloud SIEM](https://docs.datadoghq.com/security/cloud_siem/) uses these logs to detect security-sensitive activity. Requires an Anthropic Enterprise plan with the Compliance API enabled in the organization's Data and privacy settings. Without it, this dataflow collects no data. This dataflow is always on and cannot be turned off, so it appears in responses only.
          - `enabled` boolean: Whether Datadog collects this data. Always `true`, because this collection cannot be turned off.
          - `status` IntegrationAccountDataflowStatus: Read-only collection status of a dataflow.
            - `health` 'DATAFLOW_HEALTH_OK' | 'DATAFLOW_HEALTH_BROKEN' | 'DATAFLOW_HEALTH_UNKNOWN': Collection health of a single dataflow.
            - `message` string: Human-readable detail, populated when the dataflow is not healthy.
            - `updated_at` string, date-time: Time the status was last computed.
      - `name` string, required: Human-readable name of the Claude Compliance integration account.
    - `id` string, required: Server-generated unique identifier of the Claude Compliance integration account.
    - `type` 'integration-account', required: The type of the integration account resource. Always `integration-account`.

## Other responses

- `400`: Bad Request
- `403`: Forbidden
- `404`: Not Found
- `429`: Too many requests

## Changes

- **2026-11-20** `3b1c63e31740`: 4 warning
  - the optional response header `X-RateLimit-Limit` removed for the status `429`
  - the optional response header `X-RateLimit-Period` removed for the status `429`
  - the optional response header `X-RateLimit-Remaining` removed for the status `429`
  - the optional response header `X-RateLimit-Reset` removed for the status `429`
- **2026-11-20** `0c4fd355dfab`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/changes/api/v2/integration-interfaces/claude-compliance/accounts/:account_id/get.md)

---

[API](https://skmtc.dev/datadog/apis/datadog-api-v2-collection.md) - [All operations](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/llms.txt) - [OpenAPI document](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/revisions/4ba32926196d?raw)
