Open Library API
GET /api/get endpoint removal
Deprecated, no dateSubscribe to Open Library APIShare
Open Library API has deprecated the GET /api/get endpoint without a shutdown date. The endpoint remains preserved for backward compatibility, but calls to it will eventually fail. The change affects any integrations relying on this legacy interface.
Calls it hits
GET /api/get
What to use instead of these calls
Read the record as JSON directly from its own URL (/works/{id}.json, /books/{id}.json, or /authors/{id}.json), or use the Books API (/api/books).
In Open Library API's words
Legacy JSON API is deprecated and preserved for backward compatibility.
Facts
- API
- Open Library API
openlibrary.org - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Open Library API's own pages
Questions
When does this change take effect?
Open Library API deprecated GET /api/get without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Open Library 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 Open Library API 2
-
No date
GET /api/thingsEndpoint removal Deprecated, no date -
No date
GET /api/versionsEndpoint removal 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.