Have you ever….
- - Copied an API spec out of Kong Konnect, or where you manage your APIs, pasted it into your API client, and immediately wondered if it’s the latest version?
- - Sent an email to your platform team with the subject line “*which endpoint should I be using?” *and then followed up 20 minutes later with something like* “never mind, I found it”*?
- - Shipped a breaking change that wouldn’t have broken anything if the people downstream had just been working from the latest version of the spec?
- - Onboarded a new developer, watched them set up both tools, and thought “there has to be a better way….” and then just hung your head and moved on?
If you answered **yes **to any of these above….
We have great news:
**Friend, the Insomnia x Kong Konnect integration might just be for you. **
Kong Konnect is where your API truth lives. Every service, spec, version…. The canonical record of what your APIs are. The problem has been connecting your source of truth to testing it. Insomnia 13 closes this gap. With the native Kong Konnect integration, your routes, endpoints, and configurations live right where you’re already doing your API work. No more tab-hopping. No more “is this the latest version?” No more getting lost in Slack messages (well, at least for endpoints).
Connect your Kong Konnect organization directly to Insomnia and get instant, up-to-date access to everything your platform team has already set up. Your developers stay in flow. Your platform team stays sane. You keep your developer and platform workflows in harmony, without bouncing between tabs like it’s 2019.
And as your teams start connecting agentic AI to your APIs, this matters even more. An agent operating from a stale spec can call deprecated endpoints, pass outdated parameters, and fail in ways that make it nearly impossible to debug. The native Kong Konnect integration with Insomnia means the context you deliver to your agents is the same context your platform teams have already verified, versioned, and tested.