The urls you are using are correct. The first returns the list of Web App Scans based on your the filters you provided in your API request. The second will return the XML content of a scan.
Could you please try downloading all the XML scan results and, once all the scans are downloaded, launch the parsing process on each of them. That way you could separate fetching the files from parsing them.
Thanks for your fast answer. I just implemented it, so to download all the XML report and then parse them. But the same error occur with the fourth report.
Also, the files created are around 875000 lines and about 130MB... Is it possible to ask for less details in these reports? As 1900 reports of about 100MB will be a bit too much...
Thanks in advance
130 Mb for an XML scan results looks definitely too big, even for an extremely vulnerable web application.
Brice, I'll contact you to investigate deeper the issue.
Otherwise, to answer your question "Is it possible to disable the vulnerability details in this kind of scan report?", that's an option we can indeed consider if you're just interested by the QIDs and main information like vulnerable URL and param.
Let me add this to our roadmap for the scan API.