GET /v2/sites/environments/{}/plugins → endpoint removal
Kinsta API
Deprecated, no date
Kinsta has deprecated GET /v2/sites/environments/{}/plugins without a shutdown date. Calls made to this endpoint will eventually fail. The change affects any integrations querying plugin details using the deprecated path.
Calls it hits
GET /v2/sites/environments/{}/plugins
What to use instead of these calls
List plugins with GET /v2/sites/environments/{env_id}/wp-plugins instead.
In Kinsta API's words
This endpoint is deprecated. Please use
Facts
- API
- Kinsta API
api.kinsta.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Kinsta API's own pages
Questions
When does this change take effect?
Kinsta API deprecated GET /v2/sites/environments/{}/plugins without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Kinsta 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 Kinsta API 1
-
No date
GET /v2/sites/environments/{}/themesEndpoint 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.