Compliance Settings changedapi/beta/organization/compliance_settings
Nearest release: v2.1.315, published under an hour 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
Lines+4added
Lines−1removed
From line
75
where the diff opens
First seen
1 Sep 2026
this site's first read of the page
Recorded edits6to this page, all time
The whole hunk
from line 75, old and new numbered
/
from line 75
7575
7676Setting `state` to `enabled` turns on the Compliance API and begins
7777capturing organization activity events. Setting it to `disabled` turns
78both off. `state` reflects whether the Compliance API is enabled.
78both off. Access Transparency events are an exception: they are still
79captured while the Compliance API is disabled, and the Compliance API
80activity feed returns them once it is enabled again. `state` reflects
81whether the Compliance API is enabled.
7982
8083A request that sets `state` to its current value succeeds and leaves the
8184resource unchanged. A `disabled` request stays in effect until a later
No line in this hunk matches that.