We would love to see redirect management through the api.
It would allow us to link up the Redirection OR Yoast plugin to Kinsta; reducing load on the server and gives us the ability to redirect static assets (css/js/images) that would normally be served from nginx directly.
Additionally:
We’d like to set some permissions on the API key itself so it wouldn’t be allowed to do other things and restrict it to a single environment.
Or
An “internal” API on the server itself (e.g. a proxy to the public kinsta api, but with an environment scope).
Something like that might benefit Kinsta too b/c it opens a way to implement new features to the Kinsta-mu plugin.
Thank you for writing. This is something we can add as a feature request for our developers. While I cannot tell you whether this is something we will work for and if we will, when it would be available, I’ll make sure to pass your suggestion.
API-based redirect management and scoped API key permissions would be a game-changer for flexibility and server performance. An internal environment-specific API could streamline functionality further. Hope Kinsta considers these!