Update to workflow for retrieving inventory summaries with FBA Inventory API v1
Amazon now requires every paginated request to the FBA Inventory v1 endpoint `/fba/inventory/v1/summaries` to include both the original `startDateTime` (e.g., 2024-05-01T00:00:00Z) and the `nextToken`. Omitting `startDateTime` can cause duplicate or missing SKU records. Update your integration immediately to echo the timestamp on each call.
Overview
Amazon has changed the pagination rules for the FBA Inventory v1 endpoint in the Selling Partner API. Effective immediately, every request that moves to the next page must send both the original startDateTime value and the nextToken returned from the previous call. Sellers who continue to rely on the old pattern risk receiving partial or duplicated inventory data, which can distort replenishment planning and performance reporting.
Key Points
- Both parameters required — Each paginated call now mandates the inclusion of the initial
startDateTimeand the latestnextToken; omitting the timestamp leads to inaccurate results. - Time‑window enforcement — The
startDateTimeacts as a filter, ensuring that every page only contains summaries that changed after the specified moment. - Risk of stale data — Using only
nextTokenmay pull records that fall outside the intended window, producing duplicate rows or missing recent updates. - Endpoint unchanged — The modification applies to the existing
/fba/inventory/v1/summariesURL; Amazon has not introduced a new version or separate endpoint. - Code updates mandatory — Integration logic that previously sent just the token must be revised to echo the original timestamp on each subsequent request.
- Testing strongly advised — Amazon recommends running full‑cycle tests with known inventory adjustments to verify that pagination now respects the time filter.
How the Updated Retrieval Process Works
-
Initial request with startDateTime — The seller issues a GET request to
/fba/inventory/v1/summaries, supplying astartDateTimesuch as2024-05-01T00:00:00Z. The response returns the first batch of SKU summaries and, when more data exists, anextToken.- Example: A vendor asks for changes after May 1, 2024, receives 100 SKUs and a token value .
Analysis & Recommendations
Why This Matters
If `startDateTime` is not sent on subsequent pages, the API may return stale or duplicated inventory rows, leading to inaccurate stock‑out forecasts and mis‑aligned replenishment orders. Enforcing the original time filter guarantees a complete, time‑consistent snapshot of all inventory changes after the specified moment.
Key Takeaways
- Pagination now mandates both `startDateTime` and `nextToken` on every request to `/fba/inventory/v1/summaries`.
- The original `startDateTime` (e.g., 2024-05-01T00:00:00Z) must be stored and reused for each page.
- If a response lacks `nextToken` before all expected records are received, log the anomaly and halt further calls.
- The endpoint URL remains unchanged; no new version or separate endpoint was introduced.
Recommended Actions
- →In your integration code, capture the initial `startDateTime` value and add it to the query parameters for every loop iteration that includes a `ne...
- →Add a guard after each API response: if `nextToken` is null, break the pagination loop; otherwise continue with the new token.
- →Run an end‑to‑end test in your Seller Central sandbox: set `startDateTime` to yesterday, trigger a known inventory change, and verify the change ap...
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!