Skip to main content
This page is the resolution target of the RFC 9457 type URI on every invalid_cursor problem body: https://docs.get-exo.com/errors/invalid_cursor. HTTP status: 400 Bad Request.

Why it happens

Cursors are opaque. Any tampering fails here: bad base64, bad JSON, a missing key, or a timestamp that does not parse. Cursors are not portable across routes. A cursor from one list is meaningless to another.

How to fix it

  • Pass nextCursor from the previous page exactly as you received it. Do not decode, re-encode or truncate it.
  • Omit cursor to start again from the first page.