The 429 Throttle Error in Amazon’s SP-API occurs when your app exceeds rate limits under the token bucket model. This happens when you surpass requests per minute, hit burst limits, or fail to space requests properly.
Key signs:
- HTTP 429 “QuotaExceeded”
Retry-After header (e.g., 60 seconds)- Rate limit header drops to zero
Quick fix:
- Respect
Retry-After - Use exponential backoff (2ⁿ seconds)
- Queue requests (Redis/SQS)
- Cache data to reduce calls
Best solution: Replace polling with the Notifications API, cutting up to 95% of unnecessary requests and preventing throttling entirely.