Compliance Settings changedapi/organization/compliance_settings

Nearest release: v2.1.286, published 6 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here 30 Sep 2026 23:37 UTC

Lines+224added

Lines−0removed

From line — no hunk to open at

First seen 30 Sep 2026 this site's first read of the page

Recorded edits1to this page, all time

# Compliance Settings ## Get Compliance Settings ### Returns ### Example #### Response (200) ## Update Compliance Settings ### Body parameters ### Returns ### Example #### Response (200) ## Domain types ### Compliance Settings State ### Compliance Settings State Disabled ### Compliance Settings State Disabled Param ### Compliance Settings State Enabled ### Compliance Settings State Enabled Param ### Compliance Settings State Param ### Organization Compliance Settings

The whole hunk

224 lines, new page

lines

A whole new page. There's nothing to diff it against, so here is what it says.

---
title: Compliance Settings
url: https://platform.claude.com/docs/en/api/organization/compliance_settings
---

# Compliance Settings

## Get Compliance Settings

**GET** `/v1/organizations/compliance_settings`

Retrieve your organization's Compliance Settings.

Compliance Settings is a singleton resource: there is exactly one per
organization, addressed without an identifier. The `state` field reflects
whether the Compliance API is enabled. An organization with a parent
organization reads the state inherited from the parent's configuration.

### Returns

- `OrganizationComplianceSettings object`

  - `type: "compliance_settings"`

    default: compliance_settings

  - `state: ComplianceSettingsState`

    Whether the Compliance API is enabled for this organization.

    - `ComplianceSettingsStateEnabled object`

      - `type: "enabled"`

        default: enabled

    - `ComplianceSettingsStateDisabled object`

      - `type: "disabled"`

        default: disabled

### Example

```bash
curl https://api.anthropic.com/v1/organizations/compliance_settings \
    -H 'anthropic-version: 2023-06-01' \
    -H "X-Api-Key: $ANTHROPIC_API_KEY"
```

#### Response (200)

```json
{
  "state": {
    "type": "enabled"
  },
  "type": "compliance_settings"
}
```

## Update Compliance Settings

**POST** `/v1/organizations/compliance_settings`

Update your organization's Compliance Settings.

Setting `state` to `enabled` turns on the Compliance API and begins
capturing organization activity events. Setting it to `disabled` turns
both off. `state` reflects whether the Compliance API is enabled.

A request that sets `state` to its current value succeeds and leaves the
resource unchanged. A `disabled` request stays in effect until a later
`enabled` request or the organization's next provisioning action that
enables Access Transparency: enabling Access Transparency also enables
the Compliance API, which serves its activity events, so such
provisioning (including re-runs) re-enables the Compliance API even
after a `disabled` request. Automated provisioning never disables
compliance settings.

### Body parameters

- `state: ComplianceSettingsStateParam`

  Desired state. Accepts the string shorthand "enabled" or "disabled" in place of the object form; the response always returns the canonical object form.

  - `ComplianceSettingsStateEnabledParam object`

    - `type: "enabled"`

  - `ComplianceSettingsStateDisabledParam object`

    - `type: "disabled"`

### Returns

- `OrganizationComplianceSettings object`

  - `type: "compliance_settings"`

    default: compliance_settings

  - `state: ComplianceSettingsState`

    Whether the Compliance API is enabled for this organization.

    - `ComplianceSettingsStateEnabled object`

      - `type: "enabled"`

        default: enabled

    - `ComplianceSettingsStateDisabled object`

      - `type: "disabled"`

        default: disabled

### Example

```bash
curl https://api.anthropic.com/v1/organizations/compliance_settings \
    -H 'Content-Type: application/json' \
    -H 'anthropic-version: 2023-06-01' \
    -H "X-Api-Key: $ANTHROPIC_API_KEY" \
    -d '{
          "state": {
            "type": "enabled"
          }
        }'
```

#### Response (200)

```json
{
  "state": {
    "type": "enabled"
  },
  "type": "compliance_settings"
}
```

## Domain types

### Compliance Settings State

- `ComplianceSettingsState = ComplianceSettingsStateEnabled or ComplianceSettingsStateDisabled`

  - `ComplianceSettingsStateEnabled object`

    - `type: "enabled"`

      default: enabled

  - `ComplianceSettingsStateDisabled object`

    - `type: "disabled"`

      default: disabled

### Compliance Settings State Disabled

- `ComplianceSettingsStateDisabled object`

  - `type: "disabled"`

    default: disabled

### Compliance Settings State Disabled Param

- `ComplianceSettingsStateDisabledParam object`

  - `type: "disabled"`

### Compliance Settings State Enabled

- `ComplianceSettingsStateEnabled object`

  - `type: "enabled"`

    default: enabled

### Compliance Settings State Enabled Param

- `ComplianceSettingsStateEnabledParam object`

  - `type: "enabled"`

### Compliance Settings State Param

- `ComplianceSettingsStateParam = ComplianceSettingsStateEnabledParam or ComplianceSettingsStateDisabledParam`

  - `ComplianceSettingsStateEnabledParam object`

    - `type: "enabled"`

  - `ComplianceSettingsStateDisabledParam object`

    - `type: "disabled"`

### Organization Compliance Settings

- `OrganizationComplianceSettings object`

  - `type: "compliance_settings"`

    default: compliance_settings

  - `state: ComplianceSettingsState`

    Whether the Compliance API is enabled for this organization.

    - `ComplianceSettingsStateEnabled object`

      - `type: "enabled"`

        default: enabled

    - `ComplianceSettingsStateDisabled object`

      - `type: "disabled"`

        default: disabled