We’re excited to announce the general availability of Kong Insomnia 12.3!
Kong Insomnia 12.3 TL;DR? Your New Year’s resolution is probably something along the lines of “work smarter, not harder.” Our resolution is to make that actually possible. Insomnia 12.1 and 12.2 sharpened your tools, and now Insomnia 12.3 removes the friction to allow you to focus on building great endpoints. Less maintenance, more momentum.
From auto-refreshing tokens to reusable credentials, Insomnia 12.3 handles the tedious tasks so you don’t have to. [Get started for free!](https://insomnia.rest/pricing)Get started for free!
Before we jump in…
Your MCP client setups are now as portable and collaborative as everything else in Insomnia. You can now store them in Git and Cloud projects alongside the rest of your API configurations and tests. Share configurations across your team, sync between machines, maintain version history, and ensure everyone’s working with the same tested configs.
We’ve all been there, entering the same Git credentials over and over for different projects. It’s tedious and time-consuming.
With Insomnia 12.3, we’ve introduced reusable Git credentials that allow you to authenticate once and use them across all your projects. It’s a small change that adds up to significant time savings across your workflow, especially if you’re managing multiple projects or repositories.
Enterprise environments come with enterprise requirements. If your organization uses Okta or similar authentication providers that mandate state and scope parameters, Insomnia 12.3 won’t hold you back. Insomnia MCP clients fit seamlessly into your existing security infrastructure without workarounds or compromises.
SCIM tokens now automatically refresh every 90 days. If auto-refresh fails for any reason, you’ll receive notifications via email and in-app popups 20 days before expiry.
No more calendar reminders. No more surprise authentication failures in production. No more scrambling to manually rotate tokens right before they expire. Your enterprise authentication works quietly and reliably in the background. This is one less thing for you to worry about, giving you more time to focus on actual development work.
With Insomnia 12.3, we’ve redefined dozens of small interactions that, together, create a noticeably better experience.
If you’ve been heads down in your work (we get it), here’s what landed in our last two releases at the end of 2025.
We expanded our MCP capabilities with sampling and elicitation support for more flexible client interactions and added an option to disable SSL verification when connecting to MCP servers. This is particularly useful for development and testing environments where strict SSL isn’t required.
Inso CLI also leveled up with structured test results, allowing you to parse and build automation around. No more digging through free text to find out what passed or failed. We also added `--requestTimeout `to give you precise control over test execution times in automated workflows.
Stay up to date on all things Insomnia releases with our [changelog](https://insomnia.rest/changelog)changelog.
We’re already deep into planning for the upcoming Insomnia versions, and we’re excited about what’s ahead. Keep an eye out to see where Insomnia is headed in 2026!
Insomnia already holds a lot of the context that makes APIs usable: specs, environments, governance rules, requirements, and everything synced in from Kong Konnect (available as of Insomnia 13 ). Koh is a CLI that gives agents a standardized, secur
You invested in Kong Konnect. You centralized your API governance, locked down your routing, enforced your security policies, and gave your organization a single source of truth for every API in your estate. That work is done, and it is working. So
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 sh
In the last few years, Insomnia has reaffirmed its commitment to allowing developers to own their own tools, their workflows, and their data. With Insomnia 12.6, we’re taking this a step further: your collections and workspaces are now stored in a f
To follow along, you’ll need: Insomnia 13 or later An Insomnia project with an API design document An OpenAPI 3.x specification Note: In Insomnia 13, custom linting supports Spectral rulesets using the top-level rules and extends properties. Custom
We've been all ears. Your workflows clearly told us what mattered most: tabs that adapt to how you actually work, Git commits you can actually understand, and admin controls that don't require a manual to navigate. Insomnia v12.4 discards the fricti
What You'll Build To explore the new integration, I'll build a realistic API platform workflow using Konnect, Kong Gateway, and Insomnia. By the end of this tutorial, I'll have: A Konnect Control Plane (KongAir Dev) A local Kong Gateway Data Pl