Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
One change · api

compliance-sessions changed

manage-claude/compliance-sessions

Nearest release: v2.1.259, 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+7added
Lines−3removed
From line 60 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits10to this page, all time

The whole hunk

from line 60, old and new numbered
/
lines
from line 60
6060 
6161For local sessions, Anthropic records each conversation server-side as its requests reach the Claude API; nothing is installed on the device, and nothing is collected beyond the requests the client already sends to the Claude API. Local session transcripts show what Claude was asked to do and what it returned, not what happened on the device. File and network activity is visible only through the tool calls and tool results in the transcript, so activity that never reaches the API (for example, local files the session never sent) is not captured.
6262 
63In organizations that use [customer-managed encryption keys](https://platform.claude.com/docs/en/manage-claude/cmek), local session transcripts are encrypted under your key and returned as usual. While your key cannot be used (for example, because you disabled or revoked it, or because it cannot be reached), the messages endpoint returns [503 Service Unavailable](https://platform.claude.com/docs/en/manage-claude/compliance-errors#local-sessions-temporarily-unavailable) for the affected pages instead of transcript content. Those messages are never reported as `not_captured` (see [Retrieve a local session transcript](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-a-local-session-transcript)). Listing sessions and retrieving session metadata are not affected.
63In organizations that use [customer-managed encryption keys](https://platform.claude.com/docs/en/manage-claude/cmek), local session transcripts are encrypted under your customer-managed key and returned as usual. While that key cannot be used (for example, because you disabled or revoked it, or because it cannot be reached), the messages endpoint returns [503 Service Unavailable](https://platform.claude.com/docs/en/manage-claude/compliance-errors#local-sessions-temporarily-unavailable) for the affected pages instead of transcript content. Those messages are never reported as `not_captured` (see [Retrieve a local session transcript](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-a-local-session-transcript)). Listing sessions and retrieving session metadata are not affected.
6464 
6565The list endpoint returns session metadata, with no transcript content, for every linked organization your key can read. Unlike the remote session list, it has no organization or user filters: bound the results in time with the `created_at.gte` and `created_at.lt` parameters. Both take RFC 3339 timestamps with a required UTC offset, and when both are supplied, `created_at.lt` must be strictly after `created_at.gte` or the request returns [400 Bad Request](https://platform.claude.com/docs/en/manage-claude/compliance-errors#400-bad-request). A third time filter, `updated_at.gte`, bounds by last activity instead of first: it returns sessions whose last inference call is at or after the given time and combines with the `created_at` filters without changing the ordering or pagination. Use it to poll for sessions active since a previous pass, as described later in this section. New sessions and messages appear in results after a short processing delay, typically within minutes; a session that is missing immediately after it starts is not necessarily uncaptured. The following request lists sessions created since a given date.
6666 
from line 68
6868curl --fail-with-body -sS -G \
6969 "https://api.anthropic.com/v1/compliance/apps/sessions/local" \
7070 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
71 --header "anthropic-version: 2023-06-01" \
7172 --data-urlencode "created_at.gte=2026-07-01T00:00:00Z" \
7273 --data-urlencode "limit=100"
7374```
from line 144
143144 
144145curl --fail-with-body -sS \
145146 "https://api.anthropic.com/v1/compliance/apps/sessions/local/$session_id/messages" \
146 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY"
147 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
148 --header "anthropic-version: 2023-06-01"
147149```
148150 
149151```json Response
from line 289
287289curl --fail-with-body -sS -G \
288290 "https://api.anthropic.com/v1/compliance/apps/sessions/remote" \
289291 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
292 --header "anthropic-version: 2023-06-01" \
290293 --data-urlencode "created_at.gte=2026-06-01T00:00:00Z" \
291294 --data-urlencode "limit=100"
292295```
from line 355
352355 
353356curl --fail-with-body -sS \
354357 "https://api.anthropic.com/v1/compliance/apps/sessions/remote/$session_id/messages" \
355 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY"
358 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
359 --header "anthropic-version: 2023-06-01"
356360```
357361 
358362```json Response
Feedback