invalid_cursor

HTTP 400§9.2 Request shape: validation, filtering, pagination, idempotency

The cursor was not a verbatim next_cursor from a previous response. Cursors are opaque; do not construct them.

Problem shape

Every non-2xx response is an RFC 9457 application/problem+json body. The type URI below is stable and machine-matchable, so branch on the final path segment (the code) and treat the status as redundant confirmation. See the error-handling guide.

{
  "type": "https://docs.vocapable.com/errors/invalid_cursor",
  "title": "…",
  "status": 400,
  "detail": "…",
  "instance": "/v1/…"
}

← Back to the error registry