API page-size maximum reduced to 4000

The maximum page_size for paginated API endpoints has been changed to 4000, reduced from 5000. Requests that specify a larger value are capped automatically at 4000, while the default page size remains 200.

This change improves performance and scalability by reducing excessive memory consumption on certain requests and processing time for very large responses. It helps make larger data pulls more stable and faster, reducing 500 errors and avoiding unnecessary API fetch retries.

For large historical or incremental pulls, use pagination with a page_size up to 4000 and process each page sequentially. If your integration performs heavy response transformation, smaller pages may provide better memory usage and reliability.

Related Docs