Konnect Gateway Service integration in Insomnia

Enterprise and uses: Insomnia

About the Konnect integration

Starting from Insomnia 13, Enterprise users can link Insomnia to Gateway Services deployed in Konnect. The integration allows sending requests from Collections against Routes pulled from Konnect, using the Insomnia app.

After connecting and syncing your Gateway Services, Insomnia:

  • Displays the list of your control planes in Konnect as projects.
  • Nests the Gateway Services on each control plane as Collections under each project.
  • Pulls the Routes from each Gateway Service.
  • Lists the Routes in Collections for each Gateway Service.

Requirements

Available features

Collections work the same as for local Routes. The following table lists the features that allow you to link Insomnia to Konnect:

Feature

Usage

How to

Authenticate Link Insomnia to your Gateway Service
  1. From Konnect, generate a Personal Access Token (PAT).
  2. Copy the PAT.
  3. In Insomnia, open Preferences > Konnect.
  4. Paste the PAT.
  5. Click Validate & Save.
Konnect tab List your gateway services in Konnect, next to the Projects tab Open the personal workspace linked to Konnect.
Sync Pull the latest updates from Konnect into Insomnia. From the Konnect tab, click Sync.

Sync

Every time you click Sync from the Konnect tab, Insomnia pulls changes from Konnect. Syncing:

  • Doesn’t push any changes from Insomnia to Konnect.
  • Pulls changes or configurations from Konnect for the related Routes.

This preserves the local changes on Routes while allowing pulling any updates from Konnect.

Syncing preserves or resets the following data for each pulled route in Insomnia:

  • Parameters
  • Auth
  • Body
  • Custom headers
  • Scripts
  • Environment variables

Note: Overridden headers aren’t preserved — they revert to the values configured in Konnect.

FAQs

No, the Konnect integration only works with Gateway Services hosted in Konnect, not on-prem Kong Gateway.

The “Skipped Routes” Collection contains Routes using an unsupported protocol. You can’t use the Collection runner to send requests against them.

Insomnia skips Routes that use an unsupported protocol, such as SNI matching, TCP, or UDP. Insomnia displays the skipped Routes in a separate collection named “Skipped Routes”.

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!