FAQs

Why are my rows capped?

Each tier has a maximum number of rows per request. When results are truncated, the response includes an X-Rows-Capped: true header. Paginate using the after parameter with the next_cursor value from the response meta. See your tier limits with GET /v1/limits (send your key in the X-API-Key header).

Why am I getting a 402 error?

A 402 means your monthly credit allowance is exhausted. Check your current usage and reset date with GET /v1/limits (send your key in the X-API-Key header; the call is free and does not consume credits). You can upgrade your plan or wait for the next billing cycle reset.

What are the legacy tier names?

The tiers use these legacy names in some API responses or older docs:

API behavior is unchanged. If you see legacy names in older docs or responses, they map directly to the current tiers above.

How is credit cost calculated?

Each request costs: base cost + (per-row cost × rows returned). The base cost and per-row cost vary by endpoint. To minimize credit usage, request fewer rows by narrowing your time range, using filters, or setting a lower limit parameter. Call GET /v1/limits to check your remaining credits at any time.

Can I get real-time data?

The Kwery API serves historical data only. Real-time streaming is not currently available.

How far back does data go?

Historical depth depends on your tier and the source. Each exchange and data source has a different ingestion start date. Call GET /v1/sources with your key in the X-API-Key header to see available date ranges per source.

Do you support WebSocket?

Not currently. The Kwery API is a historical REST API. There are no WebSocket or streaming endpoints at this time.

Why are some fields missing from my response?

Certain fields are source-specific and only present when applicable. For example, funding_rate only appears for perpetual futures data, and strike only appears for options data. Missing fields indicate that the data point does not apply to the requested source or instrument type.