invalid_cursor API Origin: Application & API OSI layer 7 · Application Last updated 12 Oct 2026

API Error: Invalid pagination cursor (invalid_cursor / cursor expired)

The page token or cursor you passed is malformed, expired, or was generated for a different query.

Exact message you may see Invalid page tokencursor is invalidcursor expiredinvalid pagination token
Seen on: REST API

Meaning

Cursor pagination returns an opaque token (next_cursor, starting_after, pageToken) that encodes where the next page starts. The server rejects it if it was edited, URL-encoded wrongly, older than its retention window, or reused with different filters or sort order.

Slack returns invalid_cursor, Google APIs “Invalid page token”, others “cursor is invalid or expired”.

Common causes

  • Filters, sort or page size changed between pages
  • Cursor too old (expired)
  • Cursor decoded/modified or double URL-encoded
  • Cursor from one endpoint used on another

⚡ Quick fix

  1. Restart the listing without a cursor
  2. Keep every other parameter identical while paging
  3. Pass the cursor exactly as received, URL-encoding it once

Detailed fix by platform

Node.js

  1. javascript
    let cursor;
    do {
      const res = await api.list({ limit: 100, status: 'active', cursor });  // same filters every call
      handle(res.data);
      cursor = res.next_cursor;
    } while (cursor);

How to diagnose

  1. Params — Same filters/sort as the first page?
  2. Age — How long since the cursor was issued?
  3. Encoding — Compare the cursor sent with the one received

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

400 — HTTP 400 Bad Request (HTTP)400concurrent_requests_limit — API Error: Too many concurrent requests (concurrency limit reached) (API)concurrent_requests_l…CORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORSECONNRESET — Error: socket hang up / read ECONNRESET (API)ECONNRESETENOTFOUND — Error: getaddrinfo ENOTFOUND host / Name or service not known (API)ENOTFOUNDjob not found — API Error: Job / operation not found or expired (async task ID unknown) (API)job not foundlimit too large — API Error: limit must be less than or equal to 100 (page size exceeds maximum) (API)limit too largeinvalid_c…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.