Compliance Settings changedapi/organization/compliance_settings
Nearest release: v2.1.296, published an hour after 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
Lines+16added
Lines−0removed
From line
16
where the diff opens
First seen
30 Sep 2026
this site's first read of the page
Recorded edits4to this page, all time
### Headers ### Headers
The whole hunk
from line 16, old and new numbered
/
from line 16
1616whether the Compliance API is enabled. An organization with a parent
1717organization reads the state inherited from the parent's configuration.
1818
19### Headers
20
21- `"anthropic-version": optional string`
22
23 The version of the Claude API you want to use.
24
25 Read more about versioning and our version history [here](https://platform.claude.com/docs/en/api/versioning).
26
1927### Returns
2028
2129- `OrganizationComplianceSettings object`
from line 85
7785provisioning (including re-runs) re-enables the Compliance API even
7886after a `disabled` request. Automated provisioning never disables
7987compliance settings.
88
89### Headers
90
91- `"anthropic-version": optional string`
92
93 The version of the Claude API you want to use.
94
95 Read more about versioning and our version history [here](https://platform.claude.com/docs/en/api/versioning).
8096
8197### Body parameters
8298
No line in this hunk matches that.