About three months ago, we launched the beta version of the Kinsta API with functionalities that included retrieving details about WordPress, Applications, and Databases. It also allowed creating a WordPress site, clearing site cache, restarting PHP engines, and tracking these resource-intensive operation statuses.
Since then, the Kinsta API team has been dedicated to continuously expanding the API’s capabilities based largely on user input. Kristof Siket, the Development Team Lead for the Kinsta API, affirmed the crucial role of your feedback in shaping 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.”
What’s New In Kinsta API
The Kinsta API has undergone substantial growth, introducing numerous new endpoints to complement its existing services. Let’s delve into these additions, highlighting how they enrich the management of applications, WordPress sites, and databases.
Upon its initial release, the Kinsta API provided access to application-related information, including deployment and process details, contributing to analytics data. Now, this information has been organized more effectively, enabling not just retrieval of deployment details.
You can now trigger application deployment through the API with the manual deployment endpoint. This means you can now programmatically deploy an application through various means, such as the terminal, a CI/CD pipeline, or an HTTP request.
Kristof notes that “while manual deployment is not yet equivalent to a Kinsta CLI’s
kinsta deploy or
kinsta up command (which would deploy directly from the file system rather than a Git branch), it’s already a valuable feature for customizing workflows”.
Manual deployment allows you to adopt Continuous Deployment & Delivery methodologies in your DevOps workflow, as we’ve detailed in articles featuring GitHub Actions and CircleCI integration:
- How to Setup a CI/CD Pipeline with GitHub Actions and Kinsta API
- Continuous Deployment of React Apps With CircleCI & Kinsta API
The number of endpoints for WordPress hosting has grown significantly compared to other services.
Block/Unblock IP Addresses
In addition to the clear site cache and restarting PHP engine site tools, we now have endpoints for you to get the list of denied IPs and another to update the list. This simplifies the process of blocking unwanted IP addresses, whether they belong to bots, spammers, or other sources of malicious behavior.
Clearing Edge Cache
We have also created endpoints for clearing a site’s edge cache with its environment ID. This is invaluable for agencies managing multiple sites as it enables integration with tools like Slack or custom interfaces, eliminating the need to navigate numerous MyKinsta pages.
A noteworthy set of new endpoints has also been released, enabling CRUD operations for WordPress site environments. This encompasses retrieving environment details, creating WordPress site environments, creating plain environments devoid of WordPress installations, cloning existing environments, and deleting WordPress site environments.
Clone and Delete Sites
Additionally, we’ve introduced the clone site endpoint. Kristof explains that “cloning was a requested feature, particularly for agencies aiming to create sites from a base site with all necessary plugins and themes pre-installed”.
We’ve also incorporated the delete site endpoint, now complementing the create site endpoint. You can initiate site creation and deletion via the API.
We’ve written multiple guides showcasing diverse applications of the WordPress hosting endpoints:
- How To Create a WordPress Site With Kinsta API
- How To Create and Use Kinsta API Access Key
- How To Clone a WordPress Site Using the Kinsta API and React
- How To Build a Slackbot With Node.js and Kinsta API for Site Management
- Schedule Your Maintenance Tasks With Kinsta API (Clear Cache, Restart PHP Engine)
While there haven’t been any major additions to Database hosting endpoints, we have deprecated the get database by name endpoint in favor of get database with ID.
Get Started With Kinsta API Today
There is a lot that can be done with the Kinsta API. Feel free to check out our documentation to understand what’s possible with the API, how to get started, and the various permission levels and limits to the API.
Unleash the power of automation and increase efficiency with the convenience of Kinsta API. Get started today!
The post Introducing New Kinsta API Endpoints (Environment CRUD, Edge Caching, Application Deployment) appeared first on Kinsta®.
This is a companion discussion topic for the original entry at https://kinsta.com/changelog/kinsta-api-aug-2023/