Skip to content

Pagination ​

Quote endpoints use several pagination contracts. Do not rename their parameters interchangeably. Follow each endpoint’s request fields and top-level pagination object, outside data.

ContractRequestNext pageStop condition
Legacy cursor APIs, such as plate constituents and screeningnext_key + limitReturn pagination.next_key unchangedpagination.has_more=false
Lists such as ARK, industrial chains and combinable eventspage_flag + page_sizeReturn pagination.page_flag unchangedpagination.completed=true
Historical K-linesInitially end or next_time; prefer page_token for continuationReturn pagination.next_page_token; if absent, return data.next_timepagination.has_more=false
Date-range APIs, such as historical capital flowEndpoint-specific date rangeAdjust the range as documentedFollow the endpoint’s stop signal

Usually omit the first cursor or pass an empty string. Defaults and page-size limits vary by endpoint. Treat cursors as opaque strings. A short or empty page alone does not mean pagination is complete. Only some endpoints return a total.

History tokens expire after 15 minutes and bind the current user and effective query. Keep symbol, start, ktype, autype, num, extended_time and pred_side unchanged. A valid token exempts only rate rules designated for history first-page requests. See historical K-lines.

Newly designed list APIs have separate repository naming rules. The table documents implemented contracts; it does not rename existing request parameters.