Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

Kong Konnect integration in Insomnia 13: what changes for teams?


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 8151
Topic starter  

TL;DR: Developers can now test against live gateway configuration instead of stale imported specs because Insomnia 13 connects Insomnia directly to Kong Konnect, according to Kong, while custom linting now enforces API standards automatically. That shifts API governance from manual coordination to versioned, policy-backed execution, which is especially important as agentic AI starts consuming the same API context.

NHIMG editorial — what this means for NHI practitioners

Questions worth separating out

Q: How should teams keep API tests aligned with live gateway changes?

A: Teams should connect their test tools to the same control plane that governs production routes and versions.

Q: Why do stale API specs create governance risk?

A: Stale specs create governance risk because they let developers and automation test against a version of the API that no longer exists.

Q: What do security teams get wrong about API linting?

A: Many teams treat linting as a style preference, but it is actually a policy enforcement control.

Practitioner guidance

  • Bind API testing to the live control plane Use Kong Konnect as the system of record for routes, versions, and request context so tests validate current state instead of exported files.
  • Encode API standards as project-level lint rules Move style and governance checks into cloud projects so violations are caught during authoring and not deferred to manual review.
  • Check agent-facing API context before execution Verify that any AI agent or automation reads the same route and schema version that the platform team has approved for production use.

What's in the full announcement

Kong's full product release covers the operational detail this post intentionally leaves for the source:

  • A walkthrough of the native Kong Konnect connection flow for Insomnia users working against live gateway state.
  • UI-level changes that reduce onboarding friction for new developers and standardise first-request setup.
  • The custom linting experience for cloud projects, including where rules are configured and how they are enforced.
  • The Git-native workflow details introduced in Insomnia 12.6 for teams managing collections and workspaces.

👉 Read Kong's release note for Insomnia 13 and native Kong Konnect integration →

Kong Konnect integration in Insomnia 13: what changes for teams?

Explore further

View Full Forum →  |  NHI Foundation Course →



   
Quote
Share: