Skip to content
Restura Docs

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”

Postman v2.1

Collections and environments. Scripts (pm.*) carry over thanks to the QuickJS sandbox supporting the Postman API. See Postman compatibility.

Insomnia (v4 & v5)

Workspaces, requests, folders, environments. Both the classic v4 export (__export_format: 4) and the newer v5 layout (Insomnia 2024+) are detected automatically — bring your insomnia.json or .yaml 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

Both legacy .bru files in a directory (read as a whole tree) and Bruno 3.1+ collections, the latter via Bruno’s OpenCollection export.

OpenCollection

Native format — both the bundled YAML file and the directory layout. Lossless round-trip.

Export

Section titled “Export”

From the collection menu:

  • OpenCollection (YAML) — the canonical export format. A single .yml file. Lossless.
  • Postman v2.1 — for sharing with Postman users.
  • Insomnia — for sharing with Insomnia users.
  • Bruno (.bru archive) — for sharing with Bruno users.

On desktop you can also Save to Files / Sync to Disk to write the collection as an OpenCollection directory layout — one file per request, friendly for git.

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 are redacted by default. When a collection contains inline (plaintext) credentials, Restura warns before exporting and you choose Export redacted (the default — blanks every token, password, and key while keeping the auth shape: usernames, regions, key names, scopes) or explicitly opt in to Include secrets. SecretRef handles never carry plaintext and export as opaque {{handle:label}} placeholders. 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.

Section titled “Related”
ResturaThe API client that speaks every protocol.
Built byDipjyoti MetiaGitHubMIT licensed