Migration assurance
SP-API deprecated operations scanner: migration guide and scanner checklist
SP-API deprecated operations scanner explains what replaces Deprecated operations, endpoints and report constants, the removal date, the migration risks to validate, and how API Migration Guard detects the pattern.
- Target keyword: SP-API deprecated operations scanner
- Removed: Deprecated operations, endpoints and report constants
- Replacement: A scanner report with rule IDs, severity and validation steps
- Removal date: Before Amazon removes the resource
TL;DR
| Deprecated item | Removal date | Replacement | Migration risk | Scanner detection |
|---|---|---|---|---|
| Deprecated operations, endpoints and report constants | Before Amazon removes the resource | A scanner report with rule IDs, severity and validation steps | Deprecated usage can live in helper wrappers, SDK adapters, scheduled jobs and parser configs. | AMZ-ORD-ENDPOINT-001, AMZ-FIN-ENDPOINT-001, AMZ-SET-REPORT-001 |
Official status
Amazon documentation lists Deprecated operations, endpoints and report constants as in-scope for this migration. Use the official source before code freeze because deadlines and replacement details can change.
Amazon SP-API deprecation schedule Amazon SP-API deprecation schedule
Production buying workflow
This page is written for a real migration decision, not a generic lead form. The free scan should answer whether the codebase contains deadline-linked evidence; the sample report should prove the artifact shape; the paid unlock should only happen when the team needs file-level findings, remediation notes and exportable evidence.
| Stage | User question | Page evidence |
|---|---|---|
| Free scan | Do we have deprecated SP-API usage? | Rule IDs, severity and redacted evidence preview. |
| Sample report | Can engineering use the output? | HTML, JSON, CSV, SARIF and evidence package examples. |
| Paid unlock | Is the evidence actionable enough to buy? | Detailed findings, validation checklist and exportable handoff package. |
Scanner evidence contract
This page clarifies what a static scanner can and cannot prove. It should attract engineering users who search for exact operation names, then guide them into manual review for generated clients, dynamic strings and intentionally accepted exceptions.
| Evidence | Professional handling |
|---|---|
| Endpoint string | Map to module, deadline and replacement before assigning severity. |
| SDK method call | Preserve surrounding snippet and call owner so the developer can patch quickly. |
| Report type constant | Pair with parser validation because settlement risk is often downstream from the request. |
| Comment or fixture | Flag lower confidence and require reviewer decision before counting as production usage. |
Removed resource and replacement
| Old resource | Replacement | Deadline | Validation outcome |
|---|---|---|---|
| Deprecated operations, endpoints and report constants | A scanner report with rule IDs, severity and validation steps | Before Amazon removes the resource | Deprecated usage can live in helper wrappers, SDK adapters, scheduled jobs and parser configs. |
What breaks
| Area | Breakage |
|---|---|
| Code pattern | Teams miss deprecated usage hidden in source, fixtures, generated clients or parser utilities. |
| Payload or schema | Output can appear healthy while API/report payload shape changed underneath. |
| Permission or data access | Access, role, retention or payment boundaries can block the commercial handoff. |
| Pagination, status or field mapping | Pagination, deadlines and sample-data reconciliation need module-specific validation. |
Before/after example
The example is intentionally small so the migration shape is visible in a code review.
Before:
const url = "/orders/v0/orders"; const reportType = "GET_V2_SETTLEMENT_REPORT_DATA_XML";
After:
scan source, inspect typed evidence, assign migration owners and re-scan after fixesScanner detection
| Rule ID | Severity | Evidence pattern | False positive condition | Validation step |
|---|---|---|---|---|
| AMZ-ORD-ENDPOINT-001, AMZ-FIN-ENDPOINT-001, AMZ-SET-REPORT-001 | Depends on module and evidence type | Deprecated operations, endpoints and report constants | Documentation, comments, generated clients or test fixtures can require manual review. | Run a free scan across Orders, Settlement and Finances source paths. |
Migration checklist
- Run a free scan across Orders, Settlement and Finances source paths.
- Open the sample report to confirm evidence shape and export expectations.
- Prioritize blocker findings by deadline and module ownership.
- Unlock the detailed report only after the free scan shows useful evidence.
Common mistakes
- Optimizing for broad migration wording before capturing exact operation/report queries.
- Treating static analysis as absolute proof instead of tested-scope evidence.
- Sending traffic to pricing without a sample report, methodology and free scan path.
Sample report preview
The public sample report shows the same evidence shape used by paid reports: rule ID, severity, file location, redacted evidence, migration mapping, validation step and quality gate.
FAQ
Who is SP-API deprecated operations scanner for?
Developers, agencies and SaaS teams preparing Amazon SP-API cutovers.
Does the tool execute code?
No. It uses static analysis and sample validators only.
What should I do after a free scan?
Review the evidence, inspect the sample report format and unlock the detailed report if the findings are actionable.
Official sources
Validate SP-API deprecated operations scanner in your source
Run a static scan, review the sample report shape, then unlock the detailed migration report when the evidence is useful.