3 reads
Sites, environments and backups.
- Read site list and details
- Read environment details
- Read backup list
Protuno connects to Kinsta with your company API key and Company ID to check site health and, only when you allow it, clear cache or restart PHP.
No install needed for the audit. We suggest connecting a staging copy of your site first, before your live site.
Reads can run on their own. Writes ask you first by default.
3 reads
Sites, environments and backups.
2 writes
Clear cache and restart PHP. Both ask first by default.
Showing 5 of 5 capabilities
Read site list and detailskinsta.site.read
Lists the company's WordPress sites and reads details for each site the key can see.
Read environment detailskinsta.environment.read
Reads a site's environment details, including PHP version, environment name, and status.
Read backup listkinsta.backup.read
Lists manual, scheduled, and system-generated backups for an environment, including when each was taken. Backups are read only: Protuno cannot create one.
Clear site cachekinsta.cache.clear
Clears a site's cache so the next visit rebuilds it fresh.
Undo: No undo is needed or possible. Nothing is deleted, and the cache refills on the next page load.
Restart PHP enginekinsta.php.restart
Restarts an environment's PHP engine. Kinsta's own docs list this as a routine site-management action, alongside clearing cache.
Undo: There is no undo for a restart. Visitors can see brief downtime while it restarts, which is why it asks first.
Reads come first and run on their own. Cache clear and PHP restart ask you first by default, and Protuno asks before every run. Backups are read only.
Reads a site's environment details, including PHP version and environment status, before other Care checks run.
ReadsChecks a site's backup list to confirm a manual, scheduled or system backup was taken inside the expected window.
ReadsClears a site's cache once a change has gone live, so visitors see the update instead of a stale cached page.
Ask firstRestarts an environment's PHP engine when a hosting check flags it as unresponsive. It causes a brief interruption while it restarts.
Ask firstNo playbook reads it yet.
How it connects: you generate an API key in MyKinsta, find your Company ID, and paste both into Protuno. The key has the same access as the person who created it: owner, administrator or developer.
Choose an expiration or a custom start date and number of hours, give it a name and click Generate. Copy the key now, because Kinsta only shows it once.
you see: A generated key shown one time, with a prompt to copy and store it safely.
Your Company ID is the value after idCompany=.
you see: A long ID made of letters and numbers.
Protuno sends the key as a Bearer token.
you see: A confirmation that the key was accepted, or an error if it is invalid or expired.
It then shows what the key can reach: the company's sites, and the reads and writes available.
you see: A list of sites tied to the key, with reads on the left and writes on the right.
Writes ask you first by default, so clear cache and PHP restart each wait for your yes.
you see: A row for each capability, with reads running and writes set to ask first.
you see: A plain sentence and a confirm button.
Any MyKinsta company account with a user who can create API keys: company owner, administrator or developer. In Kinsta's docs the API is not gated behind a separate paid tier. Access depends on your MyKinsta role, and a key generated by a developer has narrower access than one generated by an owner or administrator.
Kinsta limits API requests per company, per IP address and for actions that create things, such as a new site. Its RateLimit response headers show where you stand, and its API docs have the current figures.
It cannot restore a backup over your live site, push staging to live, delete a site, change domains or manage company users. Its only changes are clearing the cache and restarting PHP, and both ask you first by default.
Reads reflect whatever MyKinsta currently shows for the site, environment, and backup list at the moment Protuno asks. Some actions, like cache clear or PHP restart, do not complete instantly. Kinsta returns an operation ID, and Protuno checks with Kinsta for completion rather than assuming it is done.
Most often the API key does not have access to that endpoint for the role that created it. Kinsta then returns an access error, and a company owner or administrator needs to generate a key with broader access. The other common cause is an expired key, because keys are created with a fixed expiration.
In MyKinsta, go to Company settings, then API Keys, and click Revoke next to the key. Disconnecting in Protuno does not revoke the key at Kinsta. Delete it there to cut access for good.
Capability names and default settings (on its own or ask first) are Protuno's own, and they can change as the product develops. Playbook plan, schedule and date come from Protuno's agent pages. Protuno last confirmed this connector's build status on 13 Oct 2026. Vendor limits and permissions on this page follow the vendor's public documentation as reviewed on 13 Oct 2026. The vendor's own page is the final word.
The free audit looks at the site from the outside. Connect tools afterwards, one capability at a time.
We suggest connecting a staging copy of your site first, before your live site.
That does not look like a web address. Try yourdomain.com
85 Site ChecksNo Credit Card100% Free