Moving Postman collections to Endvia

Endvia works directly with Postman files: collections are imported, edited and saved back in Postman format. There is no account and no sync server.

What can be moved?

• Postman Collection v2.0 and v2.1 files; folders, auth settings, variables, scripts and descriptions are preserved.
• Environment and globals files.
• Postman data dumps (.zip): all collections and environments in a single file.

Steps

1. In Postman, export the collection and the environments it uses as files, or download your account's data dump.
2. In Endvia, select the files with File › Import (Ctrl/⌘ O). The files are processed on this device.
3. The window that opens lists the recognised items: the number of requests and example responses for collections, the number of variables for environments. Any warnings also appear here.
4. Check the list and press the import button (e.g. Import 3 items).
5. With Request › Manage environments (Ctrl/⌘ E), choose the environment to use with the Activate button.
6. Open a request and try it with Send (Ctrl/⌘ ↵). The test results appear in the Tests section of the response.
7. To run the whole collection in sequence, open View › Runner.

What do the warnings mean?

The import window reports in advance anything in the file that Endvia cannot run, or that is missing from the file:

• Secret variables: Secret variables whose values are not in the file must be entered again in the environment.
• pm.sendRequest and require: Scripts run in an environment without network access, for at most 5 seconds. Lines containing these calls produce an error. Supported are pm.test, pm.expect, pm.environment and pm.response.
• Form fields expecting files: Files are not part of the collection; they must be selected again.

Storing in a folder

In Chrome, Edge and Opera, File › Connect to folder keeps collections as Postman files in the chosen folder. The folder can be a git repository or a shared drive. Locked (secret) values are not written to these files or to exports. The open collection can also be saved on its own as a Postman file with the File › Export: (collection name) command.

Browser versus desktop

In the browser version, 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. Sending requests without this restriction requires the desktop application, which is in preparation. gRPC, MQTT and Socket.IO are not supported.

Endvia opens right away in the browser.