Discussions

Ask a Question
Back to All

errant 403 (should be 429)

John

Mar 21, 06:39 CST

Hello.

We seem to be getting rate limited when we hit your /shipment/v1/shipments/ in a large batch. We can back off.

However, it was tricky to figure out, because when we hit to hard, the API starts returning 403s rather than 200s. I would have expected 429s in this situation. It's making us need to write custom code to handle this anomaly.

Any chance you could return 429s instead? Or help us understand this choice? Also, what is your rate limit strategy (we would like to treat it intelligently and respond in a complimentary fashion).