April 2026 SP-API Release
Amazon's April 2026 SP‑API release adds new endpoint groups (/fulfillment/v2/tracking, /advertising/v2/metrics), doubles request quotas to 10 requests per second, introduces a detailMessage field and retryAfterSeconds header, and mandates OAuth 2.0 token refresh every 30 minutes. Legacy /orders/v0 and /products/v0 will start returning 410 in October 2026 and be removed by December 2026.
Overview
Amazon released the April 2026 update for the Selling Partner API (SP‑API), adding new endpoint groups, higher rate limits, richer error data, and a mandatory OAuth 2.0 token‑rotation rule. The changes also outline a retirement schedule for several legacy endpoints. Sellers who rely on SP‑API for inventory, order, or advertising automation must adapt quickly to avoid service interruptions and to take advantage of the expanded functionality.
Key Points
- New endpoint groups — Additional API sections for fulfillment tracking and advertising metrics are now live, giving sellers more data without building separate integrations.
- Higher rate limits — Request quotas for high‑volume calls have been doubled, allowing larger catalog or order batches to complete faster.
- Richer error information — Responses now include a
detailMessagefield and aretryAfterSecondsheader, making automated troubleshooting more precise. - Legacy endpoint retirement — The
/orders/v0and/products/v0URLs will return a410 Gonestatus starting October 2026 and will be fully removed by December 2026. - OAuth 2.0 token rotation — Access tokens must be refreshed within 30 minutes, and the refresh endpoint now enforces tighter scope validation.
How SP-API Changes Work
- Expanded fulfillment tracking — A new
/fulfillment/v2/trackingendpoint delivers carrier‑specific milestones such as “out for delivery” and “customs cleared.” For example, a vendor syncing order status to its ERP can now pull real‑time tracking updates without adding a separate carrier API. - Advertising insights upgrade — The
/advertising/v2/metricsendpoint now breaks down impressions by device type (mobile, desktop, tablet). A brand manager can request a single report and instantly compare mobile versus desktop performance, eliminating the need for multiple calls. - Increased request quotas — The default Orders API limit rose from 5 to 10 requests per second per developer account. A seller who updates 10,000 orders each night can now finish the batch in roughly half the previous runtime, reducing nightly processing windows.
Analysis & Recommendations
Why This Matters
If tokens aren't refreshed every 30 minutes, integrations will face authentication failures during peak periods. The doubled quota lets large catalog or order batches finish in roughly half the time, but the upcoming 410 responses will break any script still using /v0 endpoints. New data fields from tracking and advertising endpoints enable richer reporting and better ROI analysis.
Key Takeaways
- New fulfillment tracking endpoint `/fulfillment/v2/tracking` provides carrier‑specific milestones such as "out for delivery" and "customs cleared".
- Advertising metrics endpoint `/advertising/v2/metrics` now returns impressions broken down by device type (mobile, desktop, tablet).
- Orders API request quota increased from 5 to 10 requests per second per developer account.
- OAuth access tokens must be refreshed within 30 minutes; a 25‑minute refresh interval is recommended.
Recommended Actions
- →Replace all calls to `/orders/v0` and `/products/v0` with `/orders/v1` and `/products/v1` in your codebase (see Seller Central > Developer Central ...
- →Set up an automated job to call the OAuth refresh endpoint every 25 minutes (refer to developer-docs.amazon.com > Authentication).
- →Update throttling logic to respect the new 10 rps limit and modify error‑handling to parse `detailMessage` and `retryAfterSeconds` from responses.
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!