Postman Keyboard Shortcuts
Postman's shortcuts are built around the core loop of API testing: editing a request, sending it, and reading the response, repeated dozens of times an hour during active development against an API. The send-request shortcut alone is worth learning before any other, since it's used far more frequently than anything else in the app, but the navigation shortcuts for jumping between saved requests in a large collection matter just as much once you're working with a sizeable API test suite rather than a handful of ad-hoc requests. Backend and full-stack developers integrating with third-party APIs or building their own are Postman's core audience, and within that group, anyone maintaining a large regression-style collection of saved requests against their own API gets outsized value from the navigation and search shortcuts, since jumping directly to a specific named request by typing part of its name is dramatically faster than manually expanding folders in a sidebar tree once a collection grows past a few dozen requests.
Request Management
| Action | Windows | Mac | Description |
|---|---|---|---|
| Send the current request | Ctrl+Enter | Cmd+Enter | Sends whichever request tab is currently active, the single most-used shortcut in Postman given how much of API testing is iterate-and-resend. |
| Save current request | Ctrl+S | Cmd+S | Saves changes to the current request within its collection; unsaved requests show a dot indicator on their tab, a quick visual cue that changes haven't been persisted yet. |
| Open new request tab | Ctrl+T | Cmd+T | Opens a fresh, unsaved request tab, letting you quickly test a one-off call without affecting any saved collection request. |
| Duplicate current request tab | Ctrl+Alt+D (varies by version) | Cmd+Option+D | Creates a copy of the current request as a new unsaved tab, useful for testing a variation (different parameters or headers) without altering the original saved request. |
| Close current request tab | Ctrl+W | Cmd+W | Closes the active tab; if there are unsaved changes, Postman prompts to confirm before discarding them. |
| Create new collection | Ctrl+Alt+N (varies by version) | Cmd+Option+N | Opens the new collection creation dialog, letting you group related saved requests together under a named folder structure. |
| Open Collection Runner | Ctrl+Alt+R (varies) | Cmd+Option+R | Opens the Collection Runner, which executes every request in a collection sequentially, useful for smoke-testing a full set of API endpoints in one pass rather than sending each request manually one at a time. |
Navigation
| Action | Windows | Mac | Description |
|---|---|---|---|
| Open global search | Ctrl+Shift+F (varies; often Ctrl+K) | Cmd+Shift+F | Searches across collections, environments, and saved requests by name or content, the fastest way to locate a specific request in a large workspace without manually browsing the collection tree. |
| Open environment quick-switcher | Ctrl+Alt+E (varies by version) | Cmd+Option+E | Opens a dropdown to quickly switch the active environment (e.g., from 'staging' to 'production' variable sets) without navigating to the full environment manager. |
| Switch to next request tab | Ctrl+Tab | Cmd+Option+Right (varies) | Cycles to the next open request tab, useful when you have several requests open simultaneously while testing a multi-step API flow. |
| Toggle sidebar | Ctrl+\\ | Cmd+\\ | Hides or shows the collections sidebar, freeing up horizontal space for viewing a request and its response side by side, particularly useful on smaller laptop screens. |
Frequently Asked Questions
Why does Ctrl+Enter sometimes insert a newline in a body field instead of sending the request?
If your cursor is inside a multi-line text area like the raw request body editor, some Postman versions and certain body modes can interpret Ctrl+Enter contextually, though the global send shortcut is designed to work regardless of field focus in most current versions. If it's not sending, clicking the Send button directly confirms whether it's a focus issue or a genuine settings conflict.
What happens to unsaved changes if I close a tab without saving?
Postman prompts you to save, discard, or cancel when closing a tab with unsaved changes (indicated by a small dot on the tab itself) — closing accidentally doesn't silently discard work, though pressing through the prompt quickly without reading it can still result in lost changes if you reflexively confirm.
Can I bind a custom shortcut to send a request to a specific environment?
Not directly — Postman's send shortcut always sends to whatever environment is currently active in the environment dropdown, and switching environments is a separate action. There's no built-in way to bind 'send to staging' and 'send to production' as two distinct one-key shortcuts; you switch environments first, then send.
Why do some Postman shortcuts vary between the desktop app and the web/browser version?
The Postman desktop app can claim certain key combinations more reliably as a native application, while the web version's shortcuts are constrained by whatever the hosting browser allows, occasionally causing a documented default to behave differently or require reconfiguration depending on which specific version and platform you're using.
Does Postman support running scripts before or after a request, similar to Insomnia?
Yes — Postman's pre-request and test scripts (written in JavaScript) let you dynamically set variables, generate authentication headers, or validate a response's contents automatically after it's received, a deep scripting capability that operates independently of the keyboard shortcuts covered here since scripts are written and edited within their own dedicated tabs on a request.
Can I export a request as a shareable link for a teammate who doesn't use Postman?
Yes, through Postman's collection sharing and public API documentation features, which generate a viewable (and sometimes runnable) link that a non-Postman user can open in a browser, though creating that shareable link is a menu-driven publishing action rather than something triggered by one of the individual-request keyboard shortcuts covered above.
Why does the send-request shortcut sometimes seem slower to respond on a very large request body?
The delay in that case is virtually always network and server response time rather than anything related to the keyboard shortcut itself or Postman's own processing — the shortcut triggers the send instantly, but a large payload or a slow-responding server naturally takes longer to complete the actual round trip regardless of how the request was triggered.
Is there a keyboard shortcut for viewing the raw response headers separately from the response body?
Response headers are shown in their own tab alongside the body within the response panel, and switching between these tabs is generally a mouse-click action rather than something bound to a dedicated keyboard shortcut, since the response-viewing panel wasn't designed around the same keyboard-first density as the request-editing side of the app.
Can I duplicate an entire collection folder with a keyboard shortcut in Postman?
No — duplicating a folder is done through its right-click context menu in the sidebar, selecting Duplicate, since folders can contain an arbitrary number of nested requests and sub-folders, making a full recursive duplicate too consequential an action to trigger accidentally with a single keystroke.