Import Export and Git Workspace

Import / Export and Git Workspace

Three ways to get data in and out of Getman: Postman import, Postman export, and a git-friendly workspace mirror.

Postman import

Bring in existing Postman v2.1 collections and environments.

• Collections: in the COLLECTIONS tab, use the IMPORT FROM POSTMAN (upload) button and pick one or more .json files. Each file is parsed and added; failures are reported per file.
• Environments: import Postman environment exports the same way (single object or an array).
• Imported nodes get fresh IDs, so they never collide with what you already have.
• Body types are preserved: raw, urlencoded, formdata (multipart, including file rows), and file (binary).
• Only Postman v2.1 schema is accepted; malformed files are rejected with a clear error.

Postman export

• A collection or request: from a node's menu, choose EXPORT TO POSTMAN. You get a *.postman_collection.json (schema v2.1) you can hand to anyone using Postman.
• Environments: export a single environment or all of them.
• Secret variables are masked on export (empty value, type: "secret"). See Environments and Variables.
• Saved examples are not exported — they're a local convenience that carries captured response data. See Collections.

Git-friendly workspace (desktop)

Mirror a collection to a folder of readable JSON files you can commit and review in pull requests.

What it is

• Hive is the source of truth while the app runs; the workspace folder is a mirror.
• On open, the folder is read into Getman. During the session, every change is written back out (debounced, so a burst of edits is one write).
• It's best-effort — write failures are logged, never crash your session.

Layout

Each request is a *.req.json file; each folder is a directory with a .folder.json (name, favorite, child order); a .getman/workspace.json records the root order. Names are slugified into stable, collision-free filenames.

What's omitted (on purpose)

• Response data (body/headers/status/duration) — to avoid leaking responses into git and creating churny diffs.
• Saved examples — same reason; they're local-only.

So the committed files describe requests and structure, not captured responses — clean diffs your team can review.

Using it

1. Configure the workspace folder under Settings → COLLECTIONS → Workspace settings (desktop).
2. Commit the folder (including .getman/) to git.
3. Teammates pull, open the same folder, and Getman loads the collections.
4. You can hand-edit the JSON files and reload the workspace to pick up changes.

Which should I use?

• Share with Postman users / one-off handoff: Postman export.
• Version-control collections with your team / review in PRs: git workspace.
• Move quickly between machines you own: either works; the workspace keeps history in git.