I got to spent five hours pursuing this with three call-center representatives. They each had me write a "explanation of my problem in my own words," so including this post I've written the same bug report five times. Never got to speak to an engineer. I can't recommend the experience.
They said they would raise the limit, but I haven't confirmed this.
I have two recommendations for you in the development phase:
1. Test against a report with a single page. The setup they have created takes a report ID and bundles an image of all contained pages in a zip. This takes a while and clogs up the queue. Bundling a single page is quicker, so do that instead.
2. Once you make the initial call to compile the zip file, you get a second url that you can query to see if the bundle is ready. When the zip is available, it can be downloaded multiple times, so there is no reason to keep querying the first end-point and create new ones. Just redownload the first one as long as you are testing. I spent most of my time in this stage of development, because I needed to figure how to unzip the file in-memory.
@ProductTeam, if you are reading
1. Highten the limit for requests, thank you. It is impossible to work on this iteratively.
2. Scrap the zip bundle and allow me to download a single png. The bundle is a really bad idea. Feel free to call me.