---
title: "Konnect Gateway Service integration in Insomnia"
description: Link Konnect to send requests from Insomnia to Routes in your Gateway Services.
url: "/insomnia/konnect-integration/"
canonical_url: "/insomnia/konnect-integration/"
content_type: reference
min_version:
  insomnia: '13'
tier: enterprise
products:
- Insomnia
canonical: true


---

# Konnect Gateway Service integration in 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

- An Insomnia [Enterprise account](/insomnia/enterprise/)
- A Konnect [Gateway Service](/gateway/).
- A [Personal Access Token (PAT)](/konnect-api/#personal-access-tokens) 

## Available features

Collections work the same as for local Routes. The following table lists the features that allow you to link Insomnia to Konnect:

### Authenticate
Usage: Link Insomnia to your Gateway Service
How to: |
  1. From Konnect, generate a [Personal Access Token (PAT)](/konnect-api/#personal-access-tokens).
  1. Copy the PAT.
  1. In Insomnia, open **Preferences** > **Konnect**.
  1. Paste the PAT.
  1. Click **Validate & Save**.

### **Konnect** tab

Usage: List your gateway services in Konnect, next to the **Projects** tab
How to: Open the personal workspace linked to Konnect.

### Sync
Usage: Pull the latest updates from Konnect into Insomnia.
How to: 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

- Can I use the Konnect integration with my on-prem Gateway?
  No, the Konnect integration only works with Gateway Services hosted in Konnect, not on-prem Kong Gateway.

- What is the "Skipped Routes" Collection?
  The "Skipped Routes" Collection contains Routes using an unsupported protocol. You can't use the Collection runner to send requests against them.    

- Why does Insomnia skip some Routes?
  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".


## Related Resources

- [Security at Insomnia](/insomnia/manage-insomnia/#security)

- [Enterprise](/insomnia/enterprise/)

- [Enterprise account management](/insomnia/enterprise-account-management/)

- [Enterprise user management](/insomnia/enterprise-user-management/)

- [Migrate from scratch pad to Enterprise](/insomnia/migrate-to-enterprise-from-scratchpad/)

- [Link Konnect to Insomnia](/how-to/link-konnect-to-insomnia/)


## Next Steps

- [Link a Konnect Gateway Service to Insomnia](/how-to/link-konnect-to-insomnia/)

