One change
compliance-integration-patterns
manage-claude/compliance-integration-patterns
Nearest release: v2.1.242, published 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.
manage-claude/compliance-integration-patterns Changed · +1 / -1 lines
from line 26
Both patterns share these constraints: -* Activities are queryable within 1 minute of occurring and retained for 6 years. +* Activities are queryable within 1 minute of occurring and retained for 6 years. Recording is not retroactive: it begins when the Compliance API is first enabled for your organization, and activity from before enablement is not backfilled. * The maximum `limit` for each page is 5,000. * Cursor values are opaque strings that you must not parse. * Requests are limited to 600 per minute per [parent organization](https://platform.claude.com/docs/en/manage-claude/compliance-api#how-the-compliance-api-works), shared across every key, every linked organization, and every `/v1/compliance/*` endpoint; unlike the local session endpoints, the remote session endpoints carry a second request budget on top. See [429 Too Many Requests](https://platform.claude.com/docs/en/manage-claude/compliance-errors#429-too-many-requests) for the response headers and retry contract.