page_size documents a default of 50, but the schema does not state a maximum. Clients that size their prefetch window have to guess, and guessing wrong is either wasted round-trips (too small) or a rejected request (too large).
Requested: an explicit maximum in the parameter schema/docs for page_size across the list endpoints.
Hi @krlrzv,
Thanks for bringing this up. Before going into detail, I want to make sure we’re referencing the same source, as I’ll be pulling examples from the schema defined in our OpenAPI spec here
Looking it over, each list endpoint’s page_size parameter points to one of two shared schemas, which are RequestPageSize or AssetRequestPageSize. Both define an explicit maximum.
RequestPageSize sets a maximum of 100, and AssetRequestPageSize sets a maximum of 500.
Both also share a default of 50 when no page_size is passed, which is likely why you were seeing 50 come back successfully while higher values behaved differently across endpoints.
One thing I will say is that even though the ranges are stated correctly on the individual endpoints in the API Reference, the Pagination section in our Getting Started guide states the maximum as 100, which, based on the above, is partially incorrect. So thank you for flagging this! I’ll make sure to get this corrected.