Features
Requests are prepared in tabs, sent and inspected together with their response times. Postman collections, OpenAPI and WSDL files open directly; collections are kept as Postman files on this device or in a chosen folder.
Key features
- Compatible with Postman
- Opens Postman Collection v2.0 / v2.1, environment and globals files and Postman data dumps (.zip); collections are exported in Postman format again. Folder, authorization, variable and script settings are preserved.
- OpenAPI and Swagger
- Imports OpenAPI 3 and Swagger 2 (JSON, YAML); when the address of a Swagger UI page is given, the specification is looked up on the page. When a linked source changes, the collection is updated with the differences shown.
- GraphQL
- The schema is fetched by introspection; queries are completed and validated as they are written, types are browsed in the schema documentation and fields are added to the query with a single click.
- Tests and scripts
- Pre-request and post-response scripts use pm.test, pm.expect, pm.environment and pm.response. Scripts run in a separate environment with network access disabled and a 5-second limit.
- Runner
- Runs the requests in a collection in order, with their tests; the number of iterations, a delay between requests and a CSV or JSON data file can be given. Results are saved as JSON.
- Collection documentation
- The Markdown descriptions of the collection, folders and requests become a document with a table of contents; it is saved as HTML or Markdown.
- SOAP and WebSocket
- SOAP operations are created as requests with sample envelopes from a WSDL file. Over a WebSocket connection, messages are sent and incoming ones are listed in chronological order.
- Environments and secret values
- Environment, collection and global variables are used in the form {{name}}. Locked variables are hidden and are not written to exports or to the folder.
- Authorization
- Basic, Bearer, API key (header or query) and OAuth 2.0 client credentials; authorization can be inherited from the folder or collection.
- Get as code
- A request is converted to cURL, JavaScript fetch, Python requests, Go, PHP cURL or HTTPie code. A request can also be created by pasting a cURL command.
- Inspecting responses
- Status, time (on desktop broken down into DNS, connection and first byte) and size are shown; JSON and XML are formatted, HTML opens in a safe preview, and cookies are stored and sent to the same domain.
- Storing in a folder
- Collections are kept as Postman files in a chosen folder, so they can be versioned with git and shared with a team. The last 300 requests remain in the history.
Devices and browsers
- In the desktop application requests go directly from this computer: there is no CORS restriction, headers such as Cookie and Host can be set, and certificate verification can be turned off if needed.
- In the browser requests are sent under the browser's rules: if the server does not allow it (CORS), the response cannot be read, and some headers are set by the browser.
- Storing in a folder is available in Chrome, Edge and Opera; in other browsers collections are stored in the browser and exported as files.
Keyboard shortcuts
⌘ and ⌥ are used on macOS; Ctrl and Alt on Windows and Linux.
| Shortcut | Action |
|---|---|
| Ctrl/⌘ ↵ | Send request |
| Ctrl/⌘ T | New request |
| Ctrl/⌘ W | Close tab |
| Ctrl/⌘ S | Save |
| Ctrl/⌘ O | Import |
| Ctrl/⌘ ⇧ C | Get as code |
| Ctrl/⌘ E | Environments |
On phones collections open from the ☰ button; the request and response are shown one below the other.
Get Endvia
Try it in the browser without installation; for continued use, purchase the version for macOS, Windows or Linux.