Skip to content

Every response has data.next_cursor. To get the next page, send it back unchanged as the cursor parameter. When next_cursor is null, you’ve reached the last page.

{ "success": true, "data": { "posts": ["…"], "next_cursor": "eyJpIjoiaW5zdGFncmFtIiwicCI6Mn0" } }
  • Treat the cursor as opaque. Don’t decode, edit or build it yourself.
  • Required inputs are ignored when you send a cursor. Your original inputs are stored in it. Parameters marked locked in cursor in the reference are also reused from the first call.
  • Session cookies are the exception. Endpoints that need your own login cookie (for example session_id on some Instagram endpoints) need it on every page. The endpoint page tells you which.
  • Each page is one billed call. Cap how many pages you fetch.
  • Don’t count on a cursor staying valid for a long time. Use it soon after you get it.
Terminal window
# Page 1
curl -G "https://api.scrapier.io/api/v2/google-maps/" \
-H "X-API-Key: YOUR_API_KEY" \
--data-urlencode "queries=coffee shops" \
--max-time 210
# Next page: send only the cursor from the previous response
curl -G "https://api.scrapier.io/api/v2/google-maps/" \
-H "X-API-Key: YOUR_API_KEY" \
--data-urlencode "cursor=PASTE_NEXT_CURSOR_HERE" \
--max-time 210

The result list’s key changes per endpoint (places, posts, products, reviews…). Each endpoint page names it.

For endpoints that need your own session cookie, add it next to the cursor:

params = {"cursor": data["next_cursor"], "session_id": "YOUR_SESSION_ID"}

Some endpoints return everything in one call, such as a single profile, post or transcript. Their next_cursor is always null, and the reference marks them Single lookup.