Voice to Text for Postman
You're deep in API testing. Requests are flying, responses are being validated. But documentation keeps falling behind. Every endpoint needs a description. Every collection deserves notes explaining its purpose. Blurt lets you speak your API documentation directly into Postman. Hold a button, describe the endpoint, release. Text appears where your cursor is. Your hands stay on the keyboard. Your testing momentum continues. Works everywhere in Postman that accepts text input — request descriptions, collection notes, folder descriptions, variable comments, everywhere.
The Typing Problem
API documentation always lags behind development
You just tested a new endpoint. It works. You should document what it does, what parameters it accepts, what errors it returns. But there's another endpoint waiting. Documentation can happen later. Later never comes. The collection grows. New team members join and have no idea what half these requests do. The API knowledge lives in your head instead of in Postman.
Request descriptions feel like extra work
Every request in Postman has a description field. It's right there, empty, judging you. You know exactly what this endpoint does — you could explain it in 10 seconds out loud. But typing it out feels like interrupting your real work. So the description stays blank. Weeks later, you're staring at 'POST /api/v2/sync' wondering what it actually does.
Collection notes never get written
This collection handles the entire authentication flow. Someone should explain the sequence, the dependencies, the gotchas. That someone is you. But you're testing, not writing. The collection grows to 40 requests with no overview. Onboarding a new developer means a 30-minute call explaining what a written document should already contain.
Context switching from testing to writing breaks flow
You're in the zone. Request, response, validate, next. Your brain is in API testing mode. Stopping to type documentation means switching from technical validation to prose writing. It's a different mental mode. The switch is expensive. So you skip the docs to stay in flow. The documentation debt compounds.
Environment variable purposes get forgotten
You created 15 environment variables six months ago. Some have cryptic names. Which base URL goes with which environment? What format does the auth token need? You knew this once. Now you're guessing. The variable descriptions are all empty because filling them in felt tedious when you were setting things up.
How It Works
Blurt works everywhere in Postman that accepts text — request descriptions, collection documentation, folder notes, comments, environment variable descriptions, anywhere you can type.
Hold your hotkey
Press your chosen shortcut while focused on any text field in Postman. A small indicator shows Blurt is listening.
Speak your documentation
Describe the endpoint, explain the collection, note the variable purpose. Speak naturally — Blurt handles punctuation.
Release and continue
Text appears at your cursor in Postman. No extra steps. Keep testing APIs.
Real Scenarios
Documenting endpoints while testing them
You just verified the user creation endpoint works correctly. Click into the request description, hold your hotkey: 'Creates a new user account. Requires email and password in the request body. Returns the user object with ID on success. Returns 409 if email already exists. Rate limited to 10 requests per minute.' Documentation done in 8 seconds. The endpoint is tested and documented before you move on. Future you will be grateful.
Writing collection overviews
Your authentication collection has grown to 20 requests. Time to explain how they fit together. Open the collection description, hold button: 'This collection handles the complete OAuth 2.0 flow. Start with the authorize request to get a code, then exchange it for tokens using the token endpoint. Refresh tokens expire after 7 days. See the environment variables section for required client credentials.' A 30-second voice note becomes documentation that saves hours of explanation.
Describing folder organization
You've organized requests into folders but the folder names only tell part of the story. Click the folder description, hold button: 'These endpoints are admin-only. They require the admin bearer token from the admin auth flow. Do not run these against production without explicit approval. See the admin runbook for escalation procedures.' Context that would otherwise live in your head now lives in Postman.
Annotating environment variables
Your team keeps asking what format the API key should be in. Click the variable description, hold button: 'This is the production API key. Format is 36-character UUID with hyphens. Rotate every 90 days. Current key was last rotated January 2026. Contact the platform team for new keys.' The question never gets asked again.
Adding test script comments
Your test script has some non-obvious validation logic. Position cursor in the comment area, hold button: 'This test validates that the response time is under 200 milliseconds because the SLA requires sub-200ms for tier one customers. If this fails, check the database connection pool size first.' The why behind the test is now documented.
Recording API quirks and gotchas
You just discovered this endpoint returns different error formats depending on the error type. That's worth noting. Hold button: 'Note: validation errors return a JSON array of field errors, but authentication errors return a simple message string. Handle both formats in client code.' The tribal knowledge becomes written knowledge.
Explaining pre-request scripts
Your pre-request script generates a signature. Future developers will need to understand it. Add a comment, hold button: 'This generates an HMAC-SHA256 signature using the secret key from environment variables. The signature is computed over the request body and current timestamp. Required for all authenticated endpoints.' Complex logic explained in seconds.
Why Postman 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 OAuth, HMAC, endpoints accurately | Often misinterprets technical terminology |
| Reliability | Works consistently in Postman's Electron-based interface | Can be inconsistent in non-native app contexts |
| Price | $10/month or $99/year | Free (built into macOS) |
| Free tier | First 1,000 words free | Unlimited but less reliable |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt