Orders API v2026-01-01: Breaking Changes, Enhanced Features & Call Optimization Strategies🚀 #254
Replies: 2 comments 1 reply
-
|
@Tong8s Are the related topics articles that are going to be created, currently it just links to this same discussion as I'm interested in how rate limiting will change between v0 and v2026-01-01 👀 Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
"Hi team, I am migrating from v0 to v2026-01-01. In v0, I used getOrderBuyerInfo and parsed buyerInfo.payload.BuyerTaxInfo.TaxClassifications[0].Value. In v2026-01-01, I am using GET /orders/2026-01-01/orders/{orderId}?includedData=buyerInfo. However, the buyerTaxInfo object is not appearing in the response, even for UNSHIPPED orders and with PII permissions enabled. Is BuyerTaxInfo still supported in v2026-01-01 for Brazil, or is there a new structure I should use? Thank you!" |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The new Orders API v2026-01-01 represents a significant evolution in how developers interact with Amazon order data. With the introduction of usage-based pricing, migrating to this modern API isn't just about accessing new features—it's about dramatically reducing your API call volume through smarter, more efficient data retrieval.
⚡ Why Migrate? The Efficiency Advantage
Fewer GET Calls = Better Performance
The most compelling reason to migrate is significant reduction in API call volume. Under the new pricing model, you're charged based on GET call volume. The v2026-01-01 API is specifically designed to help you minimize these calls:
1. 📦 Consolidated Data Retrieval with
includedDataParameterThe old Orders v0 API required multiple separate GET calls to retrieve complete order information:
getOrder- Basic order detailsgetOrderItems- Order items (separate call)getOrderItemsBuyerInfo- Item buyer info (separate call)That's up to 3 GET calls per order!
The new v2026-01-01 API consolidates this into a single GET call using the
includedDataparameter. You can now request all necessary data in one operation:2. 🔐 No More Restricted Data Tokens (RDT) for PII
The old API required generating a Restricted Data Token before accessing Personally Identifiable Information (PII), adding an extra API call to your workflow. The new API eliminates this requirement—PII access is now controlled through role-based permissions without additional token generation calls. Learn how to access PII data through our official guide.
3. 🔍 SearchOrders with Simplified Filtering Mechanism
The new
searchOrdersAPI v2026-01-01 reduces filtering complexity from 20+ parameters to 10 core parameters, streamlining developer integration and reducing learning curve. Key improvements include:includedDataparameter enables selective loading of data sets (BUYER, RECIPIENT, FULFILLMENT, PROCEEDS, EXPENSE, PROMOTION, CANCELLATION, PACKAGES), improving performance and reducing call volume by requesting only necessary informationmaxResultsPerPageandincludedDatabetween pagination calls, optimizing both developer experience and system efficiencyThis strategic simplification aligns with modern API design principles—fewer, more powerful parameters that encourage efficient usage patterns while maintaining full functional coverage for order retrieval workflows.
🚀 Enhanced Capabilities Beyond Call Reduction
Simplified Data Access
includedDatato specify exactly what you need (BUYER, RECIPIENT, PROCEEDS, EXPENSE, PROMOTION, CANCELLATION, FULFILLMENT, PACKAGES)Enhanced Order Information
unitPriceto indicate selling price in Amazon Retail Website, also introduces structured multi-layer financial breakdowns with proceeds/expense separation and promotion tracking that transforms flat monetary values into actionable business intelligenceOrder.packages, including carrier, tracking number, and statusBetter Fulfillment Management
shippingConstraints.cashOnDelivery, substitution preferences supported throughsubstitutionPreferencewith options like CUSTOMER_PREFERENCE, AMAZON_RECOMMENDED, DO_NOT_SUBSTITUTE, plus substitution alternatives, international shipping details supported through includingiossNumberfor EU VAT complianceDeveloper Experience Improvements
⭐ Full List of API and Attribute Changes
Please refer to our migration guide: https://developer-docs.amazon.com/sp-api/docs/orders-api-migration-guide attribute mapping part
🎯 Migration Benefits Summary
includedDataparameter🛠️ Getting Started with Migration
searchOrders,getOrderAPI with consolidatedincludedDataparameterFor step-by-step migration guidance with postman collection try-out, please check out: Migrate to Orders API v2026-01-01: Complete Developer Guide 🚀
💡 The Bottom Line
Migrating to Orders API v2026-01-01 is not just a technical upgrade—it's a strategic efficiency improvement opportunity. By consolidating multiple API calls into single requests and eliminating unnecessary token generation, you can reduce your SP-API call volume by up to 65% while gaining access to enhanced features and better data quality.
With usage-based pricing now in effect, every API call counts. The new Orders API is designed from the ground up to help you do more with less, making it the smart choice for developers who want to maintain excellent service quality while optimizing their API budget.
Start your migration today!
📚 Official Documentation & Resources
Now that Orders API v2026-01-01 is officially launched, here are the official resources to help you get started:
Core Documentation
Additional Resources
🆘 Need Help?
Support Channels
Feedback & Suggestions
We want to hear from you! Your feedback helps us improve the Orders API and our documentation.
📧 Email us at: orders-api-feedback@amazon.com
Share:
🏷️ Related Topics
Last Updated: January 2026
Please note the publication date above. While we strive to keep our content current, the rapid evolution of this topic means some details may have changed since publication. For the most up-to-date information, we encourage readers to follow the announcements in SP-API developer documentation.


3 votes ·
Beta Was this translation helpful? Give feedback.
All reactions