Amazon will sunset the SP‑API Authorization v1 endpoint and several reporting APIs on 31 March 2024. After that date calls return HTTP 410 Gone or 403 Forbidden with a “ResourceDeprecated” error. Sellers must replace URLs (e.g., /authorization/v1/token → /authorization/v2/token) and update request signatures before the deadline.
Amazon will discontinue a set of Selling Partner API (SP‑API) resources on 31 March 2024. After that date any call to the retired endpoints will return an error, which can halt order‑processing workflows and break data‑extraction pipelines. Sellers who depend on these APIs must replace the obsolete calls with the newer versions immediately to keep their operations running.
Key Points
Authorization API v1 sunset — The v1 Authorization endpoint stops responding on 31 March 2024 and returns an HTTP 410 Gone status for every request made thereafter.
Weekly deprecation table refresh — Amazon updates the public deprecation schedule each week, listing the exact sunset date for every affected resource and the recommended replacement version.
No automatic redirects — Calls to a retired URL are not forwarded to the newer endpoint; integration code must be rewritten to target the updated path.
New error codes — Starting on the sunset date, deprecated requests will fail with either a 403 Forbidden or 410 Gone response and carry a “ResourceDeprecated” error identifier.
30‑day migration window — Sellers receive at least 30 days from the public announcement to test, adjust, and deploy the required changes before the cutoff.
Reporting and fulfillment APIs affected — Endpoints that deliver order, shipment, and financial data are among those being retired, so any downstream analytics that still reference the old URLs will experience data gaps.
Signature changes required — New API versions often add extra signing headers, meaning existing HMAC calculations must be updated to match the revised specification.
Sandbox validation mandatory — Amazon requires that all revised calls be exercised in the sandbox environment before they can be promoted to production.
How Deprecation Works
Locate retired endpoints — Developers open the live deprecation table, filter for March 2024 entries (e.g., GET /authorization/v1/token), and record the suggested replacement such as .
Analysis & Recommendations
Why This Matters
If the deprecated endpoints are not replaced, order‑sync jobs, inventory updates, and financial reporting will start failing on 31 March 2024, leading to data gaps and potential sales loss. New endpoints also require extra signing headers and payload changes, so integration code must be updated and validated in sandbox to avoid production downtime.
Key Takeaways
Authorization API v1 stops responding on 31 March 2024 and returns HTTP 410 Gone.
Weekly deprecation table refresh lists exact sunset dates and replacement versions such as /authorization/v2/token.
Deprecated calls will now return 403 Forbidden or 410 Gone with the “ResourceDeprecated” error identifier.
New API versions add signing requirements (e.g., x‑amz‑access-token) and may introduce mandatory payload fields.
Recommended Actions
→Search the code repository for deprecated paths (e.g., '/authorization/v1/' or '/orders/v0/') and replace them with the new versions (e.g., '/autho...
→Update HMAC signing logic to include any new headers (like x‑amz‑access-token) per the SP‑API v2 spec and run the revised calls in the sandbox at h...
→Modify CloudWatch or third‑party alert rules to trigger on HTTP 403 or 410 responses and the “ResourceDeprecated” error string to catch any missed ...
Map to the new version — For each obsolete call the table specifies the exact operation that supersedes it; for example, the former GET /orders/v0/orders is replaced by GET /orders/v0.1/orders.
Rewrite request URLs — Code is updated to use the new path, swapping https://sellingpartnerapi-na.amazon.com/authorization/v1/token for https://sellingpartnerapi-na.amazon.com/authorization/v2/token.
Refresh request signatures — The newer version may require additional headers (e.g., x-amz-access-token) in the signature, so the HMAC generation routine is modified accordingly.
Adjust payload structures — Updated APIs can introduce mandatory fields; for instance, the v2 token request now demands a grant_type attribute that was optional in v1.
Run sandbox tests — Sellers execute the revised calls against Amazon’s sandbox, verify that the response payload matches the new JSON schema, and confirm that a “ResourceDeprecated” error no longer appears.
Update error‑handling logic — Integration code is enhanced to recognize the new 403/410 status codes and to log the “ResourceDeprecated” identifier for any lingering calls.
Promote to production before the deadline — After successful sandbox validation, the updated integration is deployed to the live environment, ensuring that scheduled jobs such as order sync, inventory updates, and financial reporting use only supported endpoints before 31 March 2024.
Context: Before vs. After
Before: An inventory‑sync script posted new SKUs to POST /listings/v2020-09-01/items, which succeeded but could not include the “fulfillmentLatency” attribute introduced in 2023.
After: The same script now calls POST /listings/v2022-04-01/items, allowing the seller to send the fulfillmentLatency field and therefore provide more accurate delivery estimates.
Before: Financial reporting pulled payment data from GET /finances/v0/payments, which stopped delivering transaction details on the sunset date, creating gaps in the accounting ledger.
After: The updated integration queries GET /finances/v1/payments, receiving a complete transaction list plus a new paymentReferenceId field that simplifies reconciliation with external bookkeeping tools.
Before: Order‑status polling used GET /orders/v0/orders and received a response format lacking the “orderCondition” property needed for advanced fulfillment routing.
After: Switching to GET /orders/v0.1/orders returns the enriched payload, enabling the seller’s routing engine to prioritize orders based on condition codes.
Before: Shipment‑tracking updates were sent to POST /shipping/v1/trackings, which did not support bulk submission and required one call per package.
After: The new POST /shipping/v2/trackings endpoint accepts an array of tracking objects, reducing API call volume and lowering latency in the carrier‑notification workflow.
Seller Impact
Sellers need to act now to safeguard their daily operations.
Audit codebases — Run a repository‑wide search for any occurrence of deprecated paths such as /authorization/v1/ or /orders/v0/ and compile a list of all matches that require replacement.
Replace calls with newer versions — For each flagged endpoint, update the URL, adjust request bodies, and modify signing logic as illustrated in the step‑by‑step guide, for example swapping the v1 token URL with the v2 equivalent.
Validate in sandbox — Execute the revised calls against Amazon’s sandbox, confirm that responses follow the new schema, and ensure that no “ResourceDeprecated” errors are returned.
Revise monitoring alerts — Adjust CloudWatch or third‑party alert rules to trigger on 403 or 410 status codes and on the “ResourceDeprecated” error string, so any missed migration is caught early.
Update documentation — Refresh internal API reference documents and runbooks to reflect the new endpoint versions, helping future developers avoid accidental re‑introduction of deprecated calls.
Schedule a staged rollout — Deploy the updated integration to a limited set of production accounts at least one week before 31 March 2024, monitor for anomalies, and then expand the rollout to all accounts.
Communicate with downstream partners — Inform any third‑party services (e.g., analytics platforms, ERP systems) that rely on SP‑API data about the endpoint changes so they can adjust their own integrations in parallel.
By completing these steps, sellers will retain uninterrupted access to critical SP‑API functionality, preserve data continuity across reporting pipelines, and avoid costly downtime that could negatively affect sales performance.
Source: developer-docs.amazon.com
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
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!