Voice to Text for Insomnia

You're testing APIs in Insomnia. Your hands are busy navigating endpoints, checking headers, tweaking parameters. But now you need to write a JSON request body, document what this collection does, or describe an environment variable. Typing prose while context-switching from technical work slows you down. Blurt lets you speak your request bodies, documentation, and descriptions directly into Insomnia. Hold a button, say what you need, release. Text appears at your cursor. Your focus stays on the API, not on typing. Works everywhere in Insomnia — request bodies, descriptions, environment variables, folder notes, anywhere you can type.

First 1,000 words free Works in all Insomnia text fields macOS only
Download Blurt Free

The Typing Problem

JSON request bodies are tedious to type

You know exactly what data the API needs. A user object with email, name, metadata fields. But typing JSON syntax — the braces, quotes, colons, commas — is slow and error-prone. One missed comma and the request fails. You could describe the whole payload in 10 seconds out loud. Instead you spend two minutes carefully typing brackets and escaping strings.

API documentation that never gets written

This collection has 47 endpoints. Each one does something specific. You could explain any of them in seconds. But typing those explanations into the description fields? That's hours of work. So the descriptions stay empty. New team members have to reverse-engineer what each endpoint does. The knowledge is in your head, but not in Insomnia.

Environment variables with cryptic names

What's the difference between API_KEY_PROD and API_KEY_STAGING_V2? You know. But three months from now, you won't. The description field is right there, waiting for context. But typing explanations for every variable feels like busywork. So you skip it. The variables remain mysterious to everyone, including future you.

Request descriptions you keep meaning to add

That POST endpoint has three required fields and two optional ones. The error codes mean specific things. You should document this. You will document this. Later. But later never comes because typing documentation while you're in testing mode requires a mental gear shift. The request stays undocumented. Onboarding new developers takes longer.

Folder organization that makes sense only to you

Your Insomnia workspace is organized by feature, then by environment, then by edge case. It makes perfect sense if you understand the system. But without folder descriptions, it's a maze to everyone else. You could explain the structure in 30 seconds. But who has time to type all that? The structure remains your personal secret.

How It Works

Blurt works in every text field within Insomnia — request bodies, descriptions, environment variables, folder notes, anywhere you can place a cursor and type.

1

Hold your hotkey

Press your chosen shortcut while focused on any text field in Insomnia. A small indicator shows Blurt is listening.

2

Speak naturally

Describe your request body, explain an endpoint, or document an environment. Blurt handles punctuation and formatting.

3

Release and done

Text appears at your cursor in Insomnia. No extra steps. Keep testing your APIs.

Real Scenarios

Documenting endpoint descriptions

You just finished testing the authentication flow. Before moving on, hold the button: 'This endpoint handles user login. Accepts email and password in the request body. Returns a JWT token valid for 24 hours. Rate limited to 5 attempts per minute. Returns 401 for invalid credentials and 429 for rate limit exceeded.' Complete documentation in 15 seconds. The next developer will understand immediately.

Explaining environment variables

Your staging environment has 12 variables. While setting them up, hold the button for each description: 'This is the OAuth client ID for the staging environment. Different from production because staging uses a separate auth provider instance. Get new values from the DevOps team if this expires.' Context preserved. No more guessing what variables mean.

Describing folder organization

Your collection has grown to 80 endpoints. Time to organize. As you create folders, hold the button: 'This folder contains all payment-related endpoints. Requires the Stripe test API key environment variable. Most endpoints need an authenticated user token in the header.' Navigation becomes self-explanatory for everyone on the team.

Adding test case notes

You discovered an edge case that breaks the API. Before you forget, hold the button in the request description: 'This tests the race condition when two users attempt to claim the same resource simultaneously. Expected behavior is that only one succeeds and the other gets a 409 conflict. Bug reference JIRA-4521.' The test case is documented before you context switch.

Explaining expected responses

You've set up response expectations for monitoring. Hold the button: 'Expected response includes a data array with at least one item. Each item must have an ID field and a created timestamp. Empty array is valid for new accounts. Missing data field indicates an API error.' Validation logic is now human-readable.

Writing collection README content

Your Insomnia collection needs onboarding instructions. Hold the button: 'Start by importing the staging environment. Run the authentication request first to get a token. That token auto-populates into all other requests. The user-management folder requires admin privileges. Contact platform team for admin test credentials.' Complete onboarding guide, dictated in under a minute.

Why Insomnia users choose Blurt over built-in dictation

Blurt macOS Dictation
Activation Single hotkey, instant start Double-tap Fn or menu bar click
Speed Text appears in under 500ms 2-3 second delay before transcription starts
Technical vocabulary Handles API terms like endpoint, OAuth, JWT accurately Often misinterprets technical jargon
Reliability Works consistently in all Insomnia text fields Sometimes fails in Electron app text inputs
Price $10/month or $99/year Free (built into macOS)
Free tier First 1,000 words free Unlimited but unreliable

Frequently Asked Questions

Does Blurt work in Insomnia's request body editor?
Yes. Blurt works in Insomnia's request body text area, whether you're writing JSON, XML, form data, or GraphQL queries. Click into the body field, hold your hotkey, speak, and the text appears. You may need to adjust syntax after dictation, but the content comes through quickly.
Can Blurt help me write JSON syntax?
Blurt is best for dictating the content and structure of your data, not the literal JSON syntax. Say 'user object with email set to test at example dot com and role set to admin' and then format it into proper JSON. You'll dictate the content quickly and add the brackets and quotes yourself. It's still faster than typing everything.
Does Blurt handle API terminology accurately?
Blurt transcribes common API terms well — endpoint, authentication, OAuth, JWT, bearer token, webhook, payload, and similar vocabulary work reliably. Highly specialized internal terms might need occasional correction, but standard API testing language comes through accurately.
Will Blurt work in environment variable fields?
Yes. Any text field in Insomnia where you can place a cursor works with Blurt. Environment variable descriptions, folder descriptions, collection notes, request descriptions — if you can type there, you can dictate there.
Can I use Blurt while Insomnia is making requests?
Absolutely. Blurt operates independently of Insomnia's network activity. You can dictate into a description field while another request is running. Blurt uses your microphone and system clipboard, which don't interfere with HTTP operations.
What if I use Postman instead of Insomnia?
Blurt works with any macOS application where you can type text, including Postman. The same hold-to-speak workflow applies. Check our Postman page for use cases specific to that tool.

Start Typing Faster Today

Free to try — no credit card required

Download Blurt