Amazon Retires Orders API v0, Replaces It With Simplified Two-Endpoint System
Amazon retired the Orders API v0 on Jan 1 2026 and introduced version v2026-01-01 with only two endpoints – GET /orders/v2026-01-01/orders/{orderId} and GET /orders/v2026-01-01/orders. The new "include" parameter lets you pull buyerInfo, lineItems and fulfillment in one call, cutting request count from four to one and lowering throttling incidents by ~40%.
Overview
Amazon has retired the original v0 version of its Selling Partner API Orders endpoint and launched a new version effective January 1 2026. The overhaul collapses ten legacy operations into just two endpoints, dramatically simplifying order retrieval for sellers. Anyone using custom code, third‑party order managers, or internal tools that pull order data must begin migration planning immediately to avoid service disruption.
Key Points
- Two endpoints replace ten — The new API offers a single “get order” call and a single “search orders” call, eliminating the need to invoke multiple operations for line items, buyer details, and shipping information.
- All data in one request — By adding an
includeparameter, developers can pull order metadata, line items, buyer address, and fulfillment details in a single response, removing the previous requirement for sequential calls. - Lower throttling consumption — Consolidating calls reduces the number of requests needed per order, freeing up throttling capacity and cutting the frequency of rate‑limit errors.
- Role‑based permissions replace RDTs — Persistent role configurations in Seller Central now grant access to personally identifiable information, removing the per‑request generation of Restricted Data Tokens.
- Native fulfillment tracking — The response now embeds carrier name, tracking number, and shipment status for FBA, Merchant‑Fulfilled, and Ship‑by‑Amazon orders, removing the need for separate fulfillment APIs.
- New data structures and naming — Pricing information is nested under a
breakdownsobject, status values shift to upper‑snake case (e.g.,UNSHIPPED), and fulfillment channel codes change fromMFN/AFNtoMERCHANT/AMAZON.
How the New Orders API Works
- Get Order (single‑order retrieval) — Submit a GET request to
/orders/v2026-01-01/orders/{orderId}with an query. For example, a seller querying order 112‑334‑556 can receive the full order record, line‑item SKUs, and tracking number in one payload.
Analysis & Recommendations
Why This Matters
Sellers who keep using the retired v0 endpoints will see 404 errors after Jan 1 2026, halting order processing. The consolidated calls reduce API quota usage and simplify code, while role‑based permissions eliminate the need for per‑request Restricted Data Tokens, saving development effort.
Key Takeaways
- The legacy ten operations are replaced by two endpoints: get order and search orders (v2026-01-01).
- The include=buyerInfo,lineItems,fulfillment flag returns all order data in a single response.
- Throttling incidents drop about 40% because the call count per order falls from four to one.
- Role‑based "Order Data Access" replaces Restricted Data Tokens for PII fields.
Recommended Actions
- →Audit your code for any /orders/v0/ URLs and replace them with the new GET /orders/v2026-01-01/orders/{orderId} or /orders endpoints, adding includ...
- →In Seller Central, go to Settings > User Permissions > Roles, create/modify a role with "Order Data Access" and assign it to the IAM user or applic...
- →Update pagination logic to check nextToken age; if older than 24 hours, discard it and request a fresh page using the original filter parameters.
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!