Skip to main content
Every tabular endpoint accepts the same shape of query parameters. Filters, sorting, pagination, and column selection are derived from the data catalog, so once you know the convention it applies to every model.

Filter operators

A filter is a query parameter named <field><Operator>. The field name is the model’s public field (as it appears in the response), and the operator is one of the suffixes below.
There is no bare-field form, and ?symbol=BTC is rejected. Always include the operator suffix (?symbolEq=BTC). Any query parameter the endpoint does not recognize returns 400, so a typo fails loudly instead of silently returning unfiltered data.

Operator suffixes

Multi-value operators (IsOneOf, IsNotOneOf, IncludesAnyOf, NotIncludesAnyOf) take a comma-separated list, and may also be repeated: ?symbolIsOneOf=BTC&symbolIsOneOf=ETH is equivalent to ?symbolIsOneOf=BTC,ETH.

Which operators a column supports

Not every column exposes every operator. The available set is constrained by the column’s type and declared per column in the catalog: The catalog endpoints list the exact operators enabled for each column, and each endpoint’s reference page documents its full parameter list.

Combining filters

Multiple filters combine with AND.

Date and time values

Any filter on a time column accepts three formats:
  • RFC3339: 2026-07-13T00:00:00Z
  • Unix seconds: 1783843200
  • YYYY-MM-DD: 2026-07-13

Sorting

Pagination

The response’s metadata reports the totals for the full filtered result set, so you can size your loop before you start:
totalRows and totalPages describe the whole filtered set, not the current page. Pair them with pageSize to know how many requests a full extract will take, or switch to CSV, which returns the page in a single downloadable file.

Selecting columns

selections takes a comma-separated list of field names and limits the response to those columns. It defaults to every field on the model, and it is supported on every endpoint, including the single-row endpoint. An unknown field name returns 400 with unknown selection field "...".
On timeseries endpoints, selections names the metric fields to return. A point always leads with its timestamp, and the remaining values are described by point_schema, so read the schema rather than assuming positions.

Response formats

Every endpoint that returns array-like data supports three encodings. Set them with the acceptFormat query parameter, or with a standard Accept header. acceptFormat takes precedence over the Accept header when both are present.
csv and jsonl return the rows as a downloadable file: the response carries a Content-Disposition: attachment header and is not wrapped in the error/data envelope. Use them for extracts and spreadsheet workflows; use JSON for application code.

Full example