Hi,
Support told me to ask here for an increase to the Rate Limit to create files via the V4 API.
Use case is a bunch of JPEG to upload, and at the current limit it makes the app quite unfit for serious business use.
My script uses exponential backoff and all and I get about 9/sec max.
Respectfully,
Dlnc1.
2025-08-21 20:45:45,937 - WARNING - Rate limited. Waiting 1 seconds...
2025-08-21 20:45:46,098 - WARNING - Rate limited. Waiting 0 seconds...
2025-08-21 20:45:46,110 - WARNING - Rate limited. Waiting 1 seconds...
2025-08-21 20:45:46,214 - WARNING - Rate limited. Waiting 0 seconds...
2025-08-21 20:45:46,224 - WARNING - Rate limited. Waiting 1 seconds...
📊 Uploaded: 265 | Failed: 0 | Speed: 6.79 files/sec | Time: 00:00:392025-08-21 20:45:47,121 - WARNING - Rate limited. Waiting 2 seconds...
2025-08-21 20:45:47,140 - WARNING - Rate limited. Waiting 0 seconds...
2025-08-21 20:45:47,150 - WARNING - Rate limited. Waiting 1 seconds...
📊 Uploaded: 269 | Failed: 0 | Speed: 6.72 files/sec | Time: 00:00:402025-08-21 20:45:47,732 - WARNING - Rate limited. Waiting 0 seconds...
7 files/sec it’s atrocious. Files are about 50kb. I mean what’s the point of allowing 2TB of data and max uploading like 350kB/s. The server is 1ms from mine in Ashburn
Hi @dnlc thank you for your feedback and I apologize that you’re running into this rate limiting issue. I’ve flagged this to our dev team to help answer your question. Once I hear back I’ll follow up.
@dnlc I spoke with the engineering team today and unfortunately it is set to 5 requests per second, as we do not differentiate between file types, so you could have 5 files that are 50Gb or 5 that are 5Kb and it will be the same for number of requests. Your points have brought up some interesting conversations and it has sparked some research into different options and variants into usage, so thank you for your feedback.
Once we have more information about timelines or directives, I’ll respond to this post.