Compliance API changedgovernment/org-admin/compliance-api
Nearest release: v2.1.305, published 3 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 16:24 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+3added
Lines−3removed
From line
16
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits9to this page, all time
The whole hunk
from line 16, old and new numbered
/
from line 16
1616
1717To create a key, enter a name and click **Create key**. The full value is shown once, immediately after creation. Copy it somewhere safe before clicking **Done**.
1818
19<Warning>
20 The full key value is shown **only once**, at creation time. If you lose it, create a new key and revoke the old one.
21</Warning>
19> [!WARNING]
20>
21> The full key value is shown **only once**, at creation time. If you lose it, create a new key and revoke the old one.
2222
2323Keys never expire on their own, so rotate them on whatever schedule your agency's policy requires. You can keep more than one key active at a time, which lets you rotate without interrupting your SIEM feed: create a new key, update your collector to use it, confirm events are still arriving, and then revoke the old key. Revoking a key takes effect immediately, and the next request made with it returns a 401.
2424
No line in this hunk matches that.