Since the launch of the Kinsta API, our team has been actively introducing new endpoints. In our most recent Changelog update, Kristof Siket, the Development Team Lead for the Kinsta API, emphasized the significant role your feedback plays in shaping our feature priorities:
“User feedback drives the prioritization of feature exposure. If you believe a specific tool or endpoint should be included in the Kinsta API, feel free to send in your feedback.”
Today, we’re thrilled to announce the addition of five new endpoints to the API (Application Programming Interface). This release expands the capability of interacting programmatically with your applications, WordPress sites, and databases, opening up exciting possibilities for streamlined management and automation.
5 New Kinsta API Endpoints
Let’s delve into the new endpoints added to the API:
1. Push Environment
The Push Environment endpoint plays a pivotal role in our WordPress Hosting service, enabling you to seamlessly transfer content from one environment to another. For instance, you can move content from a staging to a live environment.
This endpoint is good for automated workflows, where users can execute end-to-end (e2e) tests and then automatically promote the staging environment to live. It also fits perfectly into time-based release workflows, where all changes made to a default “dev” environment are released live every week.
2. Clear Kinsta CDN cache
The Kinsta CDN is enabled by default on all new sites. It leverages Cloudflare’s network, offering a number of advantages over traditional CDN providers, such as HTTP/3 support, image optimization, code minification, and more.
Previously, we introduced an endpoint to clear your WordPress site’s Edge Cache, but now we’ve added an endpoint to clear your CDN Cache, empowering you to programmatically clear both your site’s Edge cache and CDN cache.
Clearing the CDN cache is often the first step in troubleshooting when you encounter discrepancies on your site’s front end. You can opt to automate this process or create a command that can be triggered via a Slackbot.
3. Create Database
To create a database, simply specify the database type (e.g., Redis, PostgreSQL, MariaDB, or MySQL), version number, and other essential details like name, password, and username.
4. Delete Database
5. Delete Application
The Application Hosting service has seen substantial API enhancements, but one crucial endpoint was missing: Delete Application. With the addition of this endpoint, you can now effortlessly delete an application by specifying its ID programmatically.
This streamlines the process and eliminates the need to interact with the MyKinsta dashboard for routine operations.
Get Started With Kinsta API Today
There is a lot that can be done with the Kinsta API. Feel free to check out the following to understand what’s possible with the API, how to get started, and the various permission levels and limits of the API:
- Kinsta API Documentation
- Changelog 1: Introducing Kinsta API: The Power of Automation for Site Management
- Changelog 2: Introducing New Kinsta API Endpoints (Environment CRUD, Edge Caching, Application Deployment)
Unlock the boundless potential of automation and enhance efficiency with the user-friendly Kinsta API. Get started today!