Throttling
The API throttling level has been set for each Partner per API. If you try to exceed the limits, your API calls will be returned with an error: 429, “Too Many Requests”.
The following table represents the default throttling limits. If you find that you are exceeding the levels listed in the following, review your algorithms and optimize for fewer calls. If you still encounter errors, contact Partner Support and request a higher throttling threshold.
API throttling limits
Feed Type | HTTP Method | Max Requests | Max File Size per Call | Processing Time per Request |
---|---|---|---|---|
Items | POST Bulk Create / Update Items | 10 per hour | 25MB | 4 hours |
Prices | POST Bulk Price Update | 10 per hour | 10MB | 30 mins |
Promotion | POST Bulk Promo Update | 6 per day | 10MB | 30 mins |
Inventory | POST Bulk Inventory Update | 10 per hour | 5MB | 30 mins |
Scenarios where to use feed APIs / bulk update APIs vs non-feed APIs
The previous APIs are feed/bulk update APIs that are used to perform updates and tasks on a day-to-day basis, such as Bulk Item Inventory Update, Bulk Item Setup (Multiple). For these APIs, sellers have to submit the feed files as part of the feed API call and check the progress using feed status API (Marketplace Seller Feed item status API link).
Usage of other non-feed APIs, such as the Update inventory API, should be in exception scenarios only. These are primarily designed for emergency usage and are highly throttled.
Updated about 1 month ago