before_id is the first_id from a previous response changedmanage-claude/compliance-integration-patterns
Nearest release: v2.1.304, published under an hour after 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+2added
Lines−3removed
From line
61
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 61, old and new numbered
/
from line 61
6161### Cursor-driven incremental reads
6262
6363```bash cURL
64first_id="activity_01XyDMpzjS89pFZXqSFUBDr6" # first_id from a previous response
65
64# before_id is the first_id from a previous response
6665curl --fail-with-body -sS -G \
6766 "https://api.anthropic.com/v1/compliance/activities" \
6867 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
6968 --header "anthropic-version: 2023-06-01" \
7069 --data-urlencode "limit=5000" \
71 --data-urlencode "before_id=$first_id"
70 --data-urlencode "before_id=activity_01XyDMpzjS89pFZXqSFUBDr6"
7271```
7372
7473Page 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-vs-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.