SP-API January 2026: Orders API Condensed to Two Endpoints, Financial Filters Expanded
In January 2026 Amazon reduced the Orders SP‑API from ten legacy endpoints to two unified calls—getOrder and searchOrders—and added an ORDER_ID filter to listFinancialEvents. New features include the EBT_REIMBURSEMENT financial event and Brazil invoice operations (createInvoice, getInvoiceStatus, getInvoiceDocument).
Overview
In January 2026 Amazon launched a major revision of the Selling Partner API (SP‑API) Orders component. The update collapses ten legacy endpoints into just two unified calls and adds order‑level financial filters, a new EBT reimbursement event for U.S. sellers, expanded B2B analytics, and programmatic government invoicing for Brazil‑based FBA sellers. The changes cut API traffic, simplify data pulls, and introduce new compliance capabilities that sellers must address in their integration pipelines.
Key Points
- Endpoint reduction — Ten separate Orders operations are now served by the single getOrder and searchOrders endpoints, slashing request counts for typical workflows.
- Order‑ID financial filter — The listFinancialEvents operation now accepts an ORDER_ID parameter, allowing direct retrieval of financial events for a specific order.
- EBT reimbursement event — A dedicated financial event type records SNAP/EBT refunds for U.S. marketplace sellers, separating them from regular reimbursements.
- B2B analytics boost — The Sales and Traffic dataset now includes refund rates, buyer feedback scores, and A‑to‑Z claim metrics specific to Amazon Business transactions.
- Brazilian invoice API — New operations (createInvoice, getInvoiceStatus, getInvoiceDocument) let FBA sellers generate and manage Nota Fiscal invoices entirely through the API.
How the Orders API Works
-
getOrder – Full order snapshot — A single request returns order header data, line‑item details, shipping information, buyer address, and any regulated‑product flags.
- Example: Instead of three calls to fetch header, items, and shipping, a seller can request order #112‑334‑556 and receive a JSON payload containing all fields in one response.
-
searchOrders – Unified query engine — Sellers specify filters such as order status, fulfillment channel, purchase date range, or marketplace ID in one request. The API returns a paginated list that already respects the applied criteria.
Analysis & Recommendations
Why This Matters
The consolidation can cut daily API calls from ~60,000 to 10,000 for a seller processing 10k orders, preserving throttling headroom. Direct ORDER_ID financial filtering eliminates minutes‑long scans of the full ledger. Missing the EBT_REIMBURSEMENT or Brazil invoice APIs could cause SNAP reporting or Nota Fiscal compliance failures.
Key Takeaways
- Ten legacy Orders endpoints are replaced by only getOrder and searchOrders as of Jan 2026.
- listFinancialEvents now accepts an ORDER_ID parameter for order‑specific financial data.
- A new financial event type EBT_REIMBURSEMENT records SNAP/EBT refunds for U.S. sellers.
- Brazilian FBA sellers gain createInvoice, getInvoiceStatus, and getInvoiceDocument API calls for Nota Fiscal automation.
Recommended Actions
- →Update integration code in your repository: replace all calls to /orders/v0/orders, /orderItems, /shipments, etc., with getOrder or searchOrders pe...
- →Modify nightly reconciliation scripts to call listFinancialEvents with the ORDER_ID filter for each order.
- →For Brazil‑based FBA sellers, add calls to createInvoice, poll getInvoiceStatus, and download PDFs via getInvoiceDocument in the post‑shipment work...
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!