API endpoint to refresh WordPress plugin and core data

Kinsta API API Questions
1

Hello Kinsta.

We’ve built an external tool (hosted on Sevalla) that pulls WordPress core and plugin data from the Kinsta API. However, the data shown in MyKinsta can take up to 12 hours to refresh, which makes it difficult to retrieve current update information on demand.

Is there an existing API endpoint that can trigger a refresh of the WordPress core and plugin data for a site or environment?

Ideally, we would call the refresh endpoint before retrieving the latest data. A webhook confirming that the refresh has completed would also be useful, but the main requirement is an API method to initiate the refresh.

Is this currently available or planned for the API roadmap?

Thanks :slight_smile:

2

Hi @J-Langdon ! :waving_hand: Welcome to the Kinsta community.

Unfortunately at this time we don’t have a way to refresh the list outside of MyKinsta via the API; however I have brought that to our development team as a feature request, as that’s definitely a good idea. Thank you for suggesting it!

3

Thanks for coming back to me so quickly @jackirish!

The new functionality if implemeneted would be helpful for many using the Kinsta API as without the refresh ability users will still need to head back to My Kinsta. In effect, this means that yoru existing endpoints to update plugins / core is relatively pointless.

Jarrad

4

I’d secondly like this feature… at present I have a widget I’ve made for iOS that lists all my sites and any of the updates available. It’s more of a casual set up just to see at a glance… but it would be nice if it updated more often.

5

@JustJames Thanks for sharing this.

I’ll pass this along as feedback to the team. I can’t promise if or when request will be implemented, but the use case makes sense and is helpful context for the request.

6

+1 from us, and a bit more context on why it matters at scale.

We run about 560 WordPress sites on Kinsta and drive plugin updates through the API. Two things make the snapshot hard to rely on today:

  1. It can lag well past 12 hours. We’ve seen a plugin still listed with an update available days after it was updated, with last_updated_at days behind.
  2. A bulk update naming that plugin then returns success without changing anything, so automation can’t tell a real update from a no-op.

A refresh endpoint would fix both. Even before that, a field showing when the snapshot was last refreshed (per environment) would let us decide when to trust it and when to check the site itself.