before_id is the first_id from a previous response changedmanage-claude/compliance-integration-patterns
Nearest release: v2.1.309, published 13 hours 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+1added
Lines−1removed
From line
67
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits12to this page, all time
The whole hunk
from line 67, old and new numbered
/
from line 67
6767 -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
6868 -H "anthropic-version: 2023-06-01" \
6969 --data-urlencode "limit=5000" \
70 --data-urlencode "before_id=activity_01XyDMpzjS89pFZXqSFUBDr6"
70 --data-urlencode "before_id=activity_01DeFgHjKmNpQrStUvWxYzAb"
7171```
7272
7373Page through until `has_more` is `false`, then persist `first_id` from the final response and pass it unchanged as `before_id` on the next run to retrieve activities newer than the saved cursor. To walk in the opposite direction for a backfill, persist `last_id` and pass it as `after_id` instead. For the full cursor-versus-page-token reference and retry semantics, see [Paginate results](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed#paginate-results).
No line in this hunk matches that.