diff --git a/guides/activities.mdx b/guides/activities.mdx
index 56190c0..7ca7779 100644
--- a/guides/activities.mdx
+++ b/guides/activities.mdx
@@ -154,10 +154,10 @@ The activity response carries the stored prescription inline.
 ## Listing activities
 
 ```bash
-GET /v1/athletes/{athlete_id}/activities?limit=50&cursor=1737043200
+GET /v1/athletes/{athlete_id}/activities?limit=50&cursor=1737043200%7Cact_7Kq2
 ```
 
-Activities come back newest first, paginated by cursor. `limit` defaults to 50 and is clamped to 1-200; pass `pagination.next_cursor` back as `cursor` for the next page. There are no date-range or type filters; filter on your side, or track activities by `external_id`.
+Activities come back newest first, paginated by cursor. `limit` defaults to 50 and is clamped to 1-200; pass `pagination.next_cursor` back as `cursor` for the next page, URL-encoded and unchanged. There are no date-range or type filters; filter on your side, or track activities by `external_id`.
 
 ## Submitting feedback
 
diff --git a/guides/athletes.mdx b/guides/athletes.mdx
index 6912be8..b609292 100644
--- a/guides/athletes.mdx
+++ b/guides/athletes.mdx
@@ -125,10 +125,10 @@ Sending any concern key marks the concerns question answered, including when you
 ## Listing athletes
 
 ```bash
-GET /v1/athletes?limit=50&cursor=1737043200
+GET /v1/athletes?limit=50&cursor=1737043200%7Cath_3Hd9
 ```
 
-Pagination is cursor-based, not offset-based. `limit` defaults to 50 and is clamped to 1-200. The response carries `pagination.next_cursor`; pass it back as `cursor` for the next page, and stop when `pagination.has_more` is false.
+Pagination is cursor-based, not offset-based. `limit` defaults to 50 and is clamped to 1-200. The response carries `pagination.next_cursor`; pass it back as `cursor` for the next page, URL-encoded and unchanged, and stop when `pagination.has_more` is false.
 
 Add `?profile_complete=false` to list only the athletes whose profiles are still short of exact numbers. That is your nudge list.