This is a cursor-style sliding pagination. Each response includes a direct "next page" address (or offset parameter) for the subsequent request. You only need to use this provided address/parameter to fetch the next set of data seamlessly. All Real-time interfaces adopt this pagination method.
This method follows the standard MySQL pagination logic: it uses two parameters (page_num for the page number and page_size for the number of items per page) to retrieve data via the pattern LIMIT #{page_num}, #{page_size}. All EchoTik-related interfaces use this approach.Below is a simple visual breakdown to help you understand how LIMIT #{page_num}, #{page_size} works.Core ConceptThis pagination acts like "selecting a slice of data" from a full list. Think of all available data as a continuous queue of items (e.g., 1 to 20 in the example below). You use two parameters to pick which part of the queue to fetch:
Parameter
Role
Simple Definition
page_num
Starting position
"Skip the first X items" (starts at 0 for the first page)
page_size
Batch size
"Take Y items after skipping"
Visual ExampleLetโs say total available data (confidential, not returned) is 20 items: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20]
1. First Page: Get 5 items (page_num=0, page_size=5)#
These interfaces do not return a "total" count of data. The reason is that the third-party data platform treats the total data volume as confidential information. To check if youโve reached the end of the data, keep paginatingโwhen a request returns no data, it indicates youโve fetched all available results.