Launch Library 2 API
/2.2.0/* version retirement
Deprecated, no dateSubscribe to Launch Library 2 APIShare
Version 2.2.0 of the Launch Library 2 API is deprecated without an announced shutdown date, marked as unsupported with no new fixes or features. Requests to /2.2.0/* endpoints will eventually fail. Launch Library 2 API advises callers that this release is no longer maintained.
Calls it hits
/2.2.0/*
What to use instead of these calls
Call the 2.3.0 endpoints (/2.3.0/...) instead of /2.2.0/.
In Launch Library 2 API's words
**2.2.0** | ❌ **Unsupported** | [Docs (v2.2.0)](/2.2.0/swagger) | No new fixes or features. Migrate to ≥ 2.3.0.
Facts
- API
- Launch Library 2 API
ll.thespacedevs.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Launch Library 2 API's own pages
Questions
When does this change take effect?
Launch Library 2 API deprecated /2.2.0/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Launch Library 2 API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Launch Library 2 API 2
-
No date
/2.0.0/*Version retirement Deprecated, no date -
No date
/2.1.0/*Version retirement Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.