Amazon Raises SP-API Fulfillment Inbound Rate Limits by 150%
Amazon has raised the Fulfillment Inbound SP‑API rate limit from 2 to 5 requests per second (≈18,000 rps per hour) for both the v2024‑03‑20 and legacy v0 specifications, effective immediately without code changes.
Overview
Amazon has lifted the request ceiling on several Fulfillment Inbound API calls from two to five per second, a 150 % jump that activates automatically for both the current v2024‑03‑20 specification and the legacy v0 version. The change removes a long‑standing throttling bottleneck for sellers and developers who automate FBA inbound workflows, and it requires no code modifications.
Key Points
- Rate ceiling raised — The affected endpoints now accept five calls each second, up from two, equating to roughly 18,000 requests per hour when used continuously.
- Both API generations covered — The increase applies to the newest v2024‑03‑20 API as well as the older v0 version, so sellers who have not yet migrated still receive the benefit.
- Zero‑touch deployment — Amazon implemented the new limits on its servers; developers do not need to re‑authorize, adjust settings, or rewrite integration code.
- Core inbound endpoints upgraded — The getShipment, listShipmentBoxes, listDeliveryWindows, listTransportationOptions, and getShipmentOperation operations all enjoy the higher throughput.
- High‑volume users stand to gain most — Sellers handling hundreds to thousands of inbound shipments daily will notice a sharp reduction in throttling errors and latency.
How the Fulfillment Inbound Rate Limit Upgrade Works
-
Request handling window — When a client sends a request to any of the upgraded endpoints, Amazon now permits up to five calls within any one‑second interval.
- Example: A software tool that previously paced calls at 2 rps can now issue five calls in the same second, allowing three additional queries without triggering a 429 error.
-
Server‑side throttling logic — Amazon’s gateway monitors the per‑second count; once the five‑request threshold is reached, further calls are delayed until the next second begins.
- Example: If a seller submits five
listShipmentBoxesrequests at 00:00.200, a sixth request at 00:00.250 will be held back and processed at 00:01.000.
- Example: If a seller submits five
Analysis & Recommendations
Why This Matters
High‑volume sellers can now cut inbound polling latency from ~30 seconds to ~10 seconds, eliminating custom queuing layers. Parallel calls to getShipment, listShipmentBoxes, and other core endpoints can increase throughput threefold, especially during peak seasons like Q4 and Prime Day.
Key Takeaways
- Rate ceiling increased to 5 calls/sec (up from 2) for getShipment, listShipmentBoxes, listDeliveryWindows, listTransportationOptions, and getShipme...
- Both API versions—v2024‑03‑20 and v0—receive the new limit automatically, no re‑authorization needed.
- Continuous usage at the new limit equals roughly 18,000 requests per hour.
- Example before/after: polling 150 inbound containers dropped from a 30‑second cycle to about 10 seconds.
Recommended Actions
- →Review your integration code (e.g., in Seller Central > Developer Central > SP‑API settings) and reduce any back‑off delays (e.g., change 500 ms to...
- →Benchmark current request volume against the new 18,000‑per‑hour ceiling and adjust polling intervals accordingly.
- →Enable parallel execution for independent inbound calls (e.g., launch five concurrent getShipment requests) to fully utilize the 5 rps limit.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!