Pagination and filters
How paging works on the app's routes and on the connector, and the limits on page size and depth.
Lists come back one page at a time with page and page_size. The reply tells you the total, the page you got and the size used.
On the app's routes
| Route | Default page size | Largest |
|---|---|---|
GET /market/catalog/search |
20 | 200 |
GET /market/reveals |
50 | 200 |
GET /market/account/ledger |
50 | 200 |
GET /market/account/lists/{id} |
up to 300 records, no paging |
Page numbers start at 1. A page past the end is an empty page, not the last page again. A page size over the largest gives 422.
On the connector
The connector never refuses a paging request. It cuts it down so an agent that over-asks carries on instead of retrying.
page_sizeabove 100 becomes 100.- A page that would go more than 2,000 rows deep is moved back to the deepest page allowed.
- Rows are counted against your daily and monthly row ceilings. See Rate limits, credits and allowances.
Going deeper than 2,000
You cannot. To reach more records, narrow by sector, area and a filter, so that each search is a different slice. Many distinct searches are fine. Walking one broad search to its end is not.
Filters
Filters are query parameters on search and are listed in Search the book. A flag filter is 1 for on and 0 or absent for off. Text filters have a maximum length and are cut to it. The connector's search_leads accepts only sector, area, has_email, has_phone, has_website and has_director.