Changing the default API page size
Currently, if you fetch from the API and don’t specify a per_page parameter, you will get a default batch of 2000 resources. Which is, basically, just way too much.
We’re making improvements to Chargify tonight which will make a fetch of 2000 subscriptions 10 to 20 times faster. However, a sample set of 2000 subscriptions results in a JSON response that is 3.2MB of text. And that’s JSON — XML would be even bigger. Even with optimized database queries, we’re burning considerable amounts of CPU just to assemble a response of that size. In short, the default of 2000 was a bad idea.
Tonight, we’re reducing the default page size from 2000 to 200 resources, so please plan accordingly. (A sample JSON response of 200 subscriptions is 320kB in size.) You can still request larger pages (using the per_page parameter), but just be prepared to wait for it and parse the large result.
Also, make sure you note our planned downtime for tonight at 01:00EST.
