Pagination and errors

Cursor pagination

List endpoints use opaque keyset cursors, never numeric offsets.

curl --get "$LUCIM_API_URL/v1/changes" \
  --header "Authorization: Bearer $LUCIM_API_KEY" \
  --data-urlencode "limit=25" \
  --data-urlencode "cursor=$NEXT_CURSOR"

The response returns next_cursor: null when no further page is available. Treat the cursor as an opaque string and do not parse or manufacture it.

Common errors

FastAPI errors use a JSON detail field:

{
  "detail": "Entity not found or not watched by this team"
}

Status	Typical cause	Retry?
`400`	Invalid cursor or malformed operation	Fix the request
`401`	Missing or invalid credential	Replace the key
`403`	Insufficient scope or role	Use an appropriately scoped credential
`404`	Resource is absent or not visible to this tenant	Do not infer cross-tenant existence
`422`	Request fields fail validation	Fix the body or query
`429`	Rate limit exceeded	Wait for `Retry-After`
`503`	A required dependency or rate limiter is temporarily unavailable	Retry with backoff

Use bounded exponential backoff with jitter for 429 and 503 responses. Preserve the same idempotency key for an operation that explicitly supports idempotent retry.

Authentication Changes

Essentials

REST v1

Pagination and errors

Common errors

​Cursor pagination

​Common errors

Cursor pagination

Common errors