Errors and pagination

Handle Public API failures and iterate through Notes results safely.

Pagination

The Notes list endpoint uses cursor pagination. Treat next_cursor as an opaque value: do not parse it or construct one yourself.

Request the first page without a cursor.
Process items.
If next_cursor is not null, pass it as the next request’s cursor.
Stop when next_cursor is null.

Keep the same filters while walking a result set. A cursor is tied to the ordering and filters used to create it.

Errors

Status	Meaning	What to do
`400`	A query value or cursor is invalid.	Correct the request; do not retry unchanged.
`401`	The token is missing, invalid, expired, or revoked.	Supply a valid Bearer token.
`403`	The token is missing `notes:read`.	Create or use a token with the required scope.
`404`	The note does not exist or is not available to this user.	Verify the note ID and account.
`422`	One or more parameters failed validation.	Inspect the response and correct the parameters.
`5xx`	Monologue could not complete the request.	Retry with exponential backoff and jitter.

Do not automatically retry 4xx responses without changing the request. For transient network failures and 5xx responses, use bounded exponential backoff and preserve the original request filters.