GET /plugins/list* → endpoint removal
JetBrains Marketplace API
Deprecated, no date
JetBrains has deprecated GET /plugins/list* without a shutdown date. Calls matching this endpoint will eventually fail. The provider notes that this API endpoint is deprecated.
Calls it hits
GET /plugins/list*
What to use instead of these calls
Read plugin data through the Marketplace's Plugin details API, specifically GET /api/plugins/{pluginId} and its updates, or use the Plugin Repository REST client instead of the build-filtered list. Note that the documentation names no replacement for listing every plugin compatible with an IDE build.
The page names no replacement for listing every plugin compatible with an IDE build.
In JetBrains Marketplace API's words
This API endpoint is deprecated.
Facts
- API
- JetBrains Marketplace API
plugins.jetbrains.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against JetBrains Marketplace API's own pages
Questions
When does this change take effect?
JetBrains Marketplace API deprecated GET /plugins/list* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: JetBrains Marketplace 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.