Import, backup & restore
Bring requests in from OpenAPI or Postman, and write every collection out to a versioned JSON file — with a restore that previews the file first and asks whether to merge or replace.
Everything here lives in the ⋮ menu next to Collections in the sidebar.
Import
Two importers, so you don’t start from an empty app:
- OpenAPI — point it at a spec (JSON or YAML) and its operations come in as saved requests: method, path, and path parameters as placeholders already in place.
- Postman — bring an existing Postman collection across rather than re-typing it.
Imported requests land in a collection, and the sidebar switches to that collection so you can see what arrived.
Backup
Backup writes every collection to a versioned JSON file — one file, your whole library. On desktop you pick where it goes; on the web build it comes down as an ordinary browser download.
The format carries a version number so a file written today stays readable by a later build of the app.
Restore
Restoring is the operation that can lose work, so it doesn’t happen silently. Pick a file and the app first previews what’s in it — which collections, how many requests each — then asks how to apply it:
- Merge — a restored collection replaces its earlier copy by id; collections the app hasn’t seen before are added. Anything not mentioned in the file is left alone.
- Replace all — the file becomes the complete set of collections.
Between them: moving a library to a second machine is a merge; rolling a machine back to a known-good state is a replace. You choose, after seeing what the file actually contains.