Removal of selling-partner-api-docs GitHub repository
Amazon will shut down the public selling‑partner‑api‑docs GitHub repository after May 31 2024. After that date every direct link (e.g., https://raw.githubusercontent.com/amazon/selling-partner-api-docs/main/spec.md) returns a 404, and all open issues are automatically copied to the selling‑partner‑api‑models repository.
Overview
Amazon will shut down the public selling‑partner‑api‑docs repository on GitHub after May 31 2024. From that day forward the repository, its markdown files, and its issue tracker will disappear from the web. Sellers and developers who depend on the repo for reference material, sample code, or community discussions must move to the new location to keep their workflows intact.
Key Points
- Decommission deadline — After May 31 2024 any direct link to the old repository returns a 404 error, breaking bookmarks and automated fetches.
- New home for issues — All open tickets, bug reports, and feature suggestions posted before the cutoff are automatically copied to the selling‑partner‑api‑models repository, preserving authorship and comment history.
- Official docs remain — Core API reference pages continue to be hosted on Amazon’s developer portal, but community‑generated markdown files and examples are no longer served from GitHub.
- Build pipelines at risk — CI/CD jobs, Docker builds, or scripts that pull raw files from the retired repo will fail unless they are retargeted to the new repository or to the static docs site.
- No GitHub archive — The commit history of the removed repository will not be retained on GitHub; teams needing a historical record must create a local mirror before the deadline.
- Support moves — Future questions about the content will be answered through the issue tracker of the selling‑partner‑api‑models repository instead of the old discussion board.
How the Transition Works
- Issue migration — On the decommission day Amazon runs a script that copies every open issue from the old repo into the selling‑partner‑api‑models repo, keeping the original timestamps and comment threads; for example, a bug report filed on April 15 will appear unchanged in the new issue list.
- Repository deletion — Immediately after the migration the selling‑partner‑api‑docs repository is removed from GitHub, causing all URLs that pointed to it to become inactive; a curl command that previously fetched will now return a 404.
Analysis & Recommendations
Why This Matters
Sellers and developers relying on the repo for markdown specs, sample code, or issue tracking will see build failures and broken links after May 31 2024. Without updating URLs or archiving the repo, compliance audits and automated pipelines may be disrupted.
Key Takeaways
- The decommission deadline is May 31 2024; after that the selling‑partner‑api‑docs repo returns 404 for all URLs.
- Open issues are migrated to the selling‑partner‑api‑models repository, preserving timestamps and comments.
- GitHub will not retain the commit history; teams must create a local mirror before the cutoff.
- Official API reference stays on Amazon’s developer portal, while community markdown moves to the selling‑partner‑api‑models repo.
Recommended Actions
- →Run `git clone --mirror https://github.com/amazon/selling-partner-api-docs.git` and store the mirror internally before May 31 2024.
- →Update all scripts, Dockerfiles, and CI jobs to replace `github.com/amazon/selling-partner-api-docs` with `github.com/amazon/selling-partner-api-mo...
- →Search internal wikis and partner portals for old repo links and replace them with the new repository URL or Amazon Developer Documentation URLs.
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!