Postman v2.1
Collections and environments. Scripts (pm.*) carry over thanks to the QuickJS sandbox supporting the Postman API. See Postman compatibility.
Import & export
Restura imports from the major API client formats and exports to OpenCollection — the open, vendor-neutral collection spec — as well as back to Postman v2.1.
Import
Section titled “Import”Insomnia
Workspaces, requests, folders, environments. Bring your insomnia.json straight in.
OpenAPI / Swagger
Schema-driven import. Every operation in the spec becomes a request; example bodies pre-fill where available.
Hoppscotch
Native Hoppscotch JSON.
Bruno (3.1+)
Bruno .bru files in a directory. Restura reads the whole tree.
OpenCollection
Native format — both the bundled JSON layout and the directory layout. Lossless round-trip.
Export
Section titled “Export”- OpenCollection (bundled JSON) — the canonical export format. Lossless.
- OpenCollection (directory layout) — one file per request, friendly for
git. - Postman v2.1 — for sharing with Postman users.
Auth schemes that exist in Restura but not in the target format are persisted via the OpenCollection extensions field so they round-trip.
Secret redaction on export
Section titled “Secret redaction on export”Exports run through a redactor that strips inline secret values, replacing them with environment placeholders where possible ({{api_token}}). SecretRef handles, by definition, never carry plaintext, so they export safely. Always re-check an export before committing it to a public repo.
OpenCollection — why it exists
Section titled “OpenCollection — why it exists”Postman locked their format and Insomnia did too. OpenCollection is an open spec for API collections — see the reference — designed for portability between tools, version control, and CI.
Related
Section titled “Related”- Collections — how collections are organised.
- Postman compatibility — script-level compatibility details.
- OpenCollection — the format spec.