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.
| Contract | Request | Next page | Stop condition |
|---|---|---|---|
| Legacy cursor APIs, such as plate constituents and screening | next_key + limit | Return pagination.next_key unchanged | pagination.has_more=false |
| Lists such as ARK, industrial chains and combinable events | page_flag + page_size | Return pagination.page_flag unchanged | pagination.completed=true |
| Historical K-lines | Initially end or next_time; prefer page_token for continuation | Return pagination.next_page_token; if absent, return data.next_time | pagination.has_more=false |
| Date-range APIs, such as historical capital flow | Endpoint-specific date range | Adjust the range as documented | Follow 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.