Overview

Amazon is decommissioning two Subscribe & Save report endpoints in the Selling Partner API (SP‑API), giving sellers roughly five months to adjust before the services stop responding. The change takes effect globally and forces developers to migrate to the newer Replenishment API or switch to manual tracking via Seller Central. Sellers who rely on automated subscription data must act now to avoid disruptions.

Key Points

• Report types retired — The GET_FBA_SNS_FORECAST_DATA and GET_FBA_SNS_PERFORMANCE_DATA endpoints will cease operation.
• Phased shutdown — Starting around June 25 2025 the endpoints will return empty payloads; full removal is scheduled for November 11 2025.
• Global impact — All Amazon marketplaces are affected, so sellers with listings in multiple regions must update every integration.
• No legacy support — After November 2025 there will be no fallback or legacy version of these reports.
• Replacement option — Amazon recommends the Replenishment API v2022‑11‑07 as the consolidated source for forecast and performance data.

What's Changing

1. Endpoint deprecation — The two legacy report calls will first deliver empty responses, meaning any scheduled job that pulls forecast or performance data will receive a blank file instead of the expected CSV or JSON. For example, a seller who runs a nightly Lambda function to download GET_FBA_SNS_FORECAST_DATA will see the function succeed but receive no rows, triggering downstream alerts.
2. Full removal — After the empty‑response window, the API routes for both reports are eliminated. Any request made to the old URLs will return a 404 error, breaking integrations that have not been updated. A third‑party inventory platform that still references GET_FBA_SNS_PERFORMANCE_DATA will start logging “endpoint not found” errors for all its customers.
3. Shift to Replenishment API — The new Replenishment API merges forecast and performance information into a single set of endpoints, delivering real‑time demand signals and richer metrics such as subscription churn rate and projected weekly units. For instance, a seller can now call the endpoint to receive both the next‑30‑day demand estimate and the historical conversion rate in one response.