Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Developer Platform 22 Oct 2026
One change · api

compliance-org-data changedmanage-claude/compliance-org-data

Nearest release: v2.1.308, published 2 hours 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+8added
Lines−8removed
From line 29 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits7to this page, all time

The whole hunk

from line 29, old and new numbered
/
lines
from line 29
2929 -H "anthropic-version: 2023-06-01"
3030```
3131 
32```json Response
32```text Response wrap
3333{
3434 "data": [
3535 {
from line 80
8080 --data-urlencode "limit=500"
8181```
8282 
83```json Response
83```text Response wrap
8484{
8585 "data": [
8686 {
from line 115
115115 -H "anthropic-version: 2023-06-01"
116116```
117117 
118```json Response
118```text Response wrap
119119{
120120 "data": [
121121 {
from line 145
145145 -H "anthropic-version: 2023-06-01"
146146```
147147 
148```json Response
148```text Response
149149{
150150 "data": [
151151 {
from line 180
180180 -H "anthropic-version: 2023-06-01"
181181```
182182 
183```json Response
183```text Response wrap
184184{
185185 "data": [
186186 {
from line 207
207207 -H "anthropic-version: 2023-06-01"
208208```
209209 
210```json Response
210```text Response wrap
211211{
212212 "data": [
213213 {
from line 243
243243 
244244The response is a list of typed setting rows, and which rows appear varies by organization: a setting the organization's administrators cannot change, because it is controlled by Anthropic policy or not available to the organization, is omitted from the list. Treat a missing row as "not controllable by this organization's administrators", not as "off". The following abridged example shows three of the rows a response can contain:
245245 
246```json Response
246```text Response wrap
247247{
248248 "type": "effective_organization_settings",
249249 "organization_id": "91012d09-e48b-438e-a489-1bebfd8fa6f9",
from line 287
287287 
288288Each row carries `name`, `type`, and `value`; the `type` field (`boolean`, `integer`, `string_list`, `provisioning_mode`, or `data_retention`) tells you the shape of `value`. The full list of setting names, and the `value` schema for each type, is in [Get effective organization settings](https://platform.claude.com/docs/en/api/compliance/organizations/settings/retrieve) in the API reference.
289289 
290The `api_keys` array lists every Compliance Access Key configured for your parent organization, so the same list is returned regardless of which linked organization you query. Each entry carries the key's `type` (`compliance_api_key`), `id`, `name`, `scopes`, `is_active` flag, `created_at` and `expires_at` timestamps, and `created_by_id` (the ID of the user who created the key; might be `null`). The key's secret value is never returned. Deactivated keys are included with `is_active: false` so you can review keys that previously had access, and keys that carry only the retired `read:compliance_org_settings` scope remain in the list for audit and cleanup visibility even though that scope no longer grants access.
290The `api_keys` array lists every Compliance Access Key configured for your parent organization, so the same list is returned regardless of which linked organization you query. Each entry carries the key's `type` (`compliance_api_key`), `id`, `name`, `scopes`, `is_active` flag, `created_at` and `expires_at` timestamps, and `created_by_id` (the ID of the user who created the key, or `null`). The key's secret value is never returned. Deactivated keys are included with `is_active: false` so you can review keys that previously had access, and keys that carry only the retired `read:compliance_org_settings` scope remain in the list for audit and cleanup visibility even though that scope no longer grants access.
291291 
292292The top-level `organization_id` is the organization's bare UUID: the same value as `uuid` in the organizations list, not the `org_`-prefixed form that `organization_id` carries on Activity Feed, chat, and project records (see the [organization identifier table](https://platform.claude.com/docs/en/manage-claude/compliance-org-data#list-organizations)).
293293 
Feedback