Skip to main content

Read API responses and follow pagination safely

Handle missing coverage, decimal strings, cursors and conditional requests correctly.

A successful status describes the HTTP request, not complete source coverage. Read the response’s data, missing and meta together.

Keep the full meaning

Preserve decimal values as strings and retain source, region, native identity, units, state and timestamps. A probability is not decimal odds. Nonempty data may still have missing or incompatible outcomes.

Follow pages explicitly

When meta.next_cursor is nonempty, pass it unchanged as cursor with the same namespace and filters. Set your own page/row limit. Stop on errors or repeated cursors; an empty cursor ends traversal. Each eligible successful data page can consume one credit.

A 409 can mean the cursor’s query or underlying semantics changed. Decide whether to start a fresh traversal. Do not silently splice the new traversal into old data.

Use conditional requests carefully

For the identical query, you may send a previous ETag as If-None-Match. A 304 has no body and is free. Reuse only the matching cached representation; current access and freshness still apply. Caching cannot keep a withdrawn or stale price active.

See Errors, credits and pagination. Keep the request ID when investigating an unexpected result.

Did this answer your question?