invalid_cursor
422 Unprocessable Content The pagination cursor is not valid.
When you get it
The pagination cursor is not valid. It is always answered with HTTP 422 - one code means one status, so a client may key its handling on either.
Fields it carries
Inside each errors[] entry, beside pointer:
parameter- The query parameter the failure is about - the query-side twin of `pointer`.
reason- The machine-readable sub-case, when one code covers several. Branch on it.
A field is omitted when the server genuinely does not know it - an absent member is never the same as an empty one.
How to fix it
The request was well-formed but a value is not acceptable. The fields above name the offending value and what would be accepted - fix the request and retry.
Shape
{
"type": "https://api2.host-tracker.com/problems/invalid-cursor",
"title": "The pagination cursor is not valid.",
"status": 422,
"code": "invalid_cursor",
"errors": [
{ "parameter": …, "reason": … }
]
}