Restura imports from the major API client formats and exports to OpenCollection — the open, vendor-neutral collection spec — as well as Postman (v3 folder / zip, or v2.1 single file), Insomnia, and Bruno.
Drop a file anywhere in the window to import it: Restura detects the format (Postman, Insomnia, OpenAPI, Hoppscotch, Bruno, .http, HAR, OpenCollection) and opens the import review — nothing is added until you confirm. You can also pick a format and choose a file from Import collection.
The review shows the collection’s request and folder counts (the whole tree, nested folders included) and the first five warnings, with how many more there are. If a collection with the same name already exists, choose Keep both (the import is renamed, e.g. Orders 2) or Replace the existing collection (its linked workflows are removed). Nothing in the import is executed. After you confirm, the banner names the imported collection — with Show all and Copy warnings when there are warnings — and the sidebar scrolls to it.
Collections and environments. v3 is the multi-file YAML folder format; see Postman import and Postman v3 export. 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. Nunjucks references {{ _.var }} and {{_['var']}} become {{var}} in URLs, params, headers, bodies, auth and environment values (nested environment objects flatten to dotted keys); other template tags and filters are kept as written, with a warning. GraphQL requests’ application/graphql JSON envelope is split into query, variables and operation name on import, and written back on export.
OpenAPI / Swagger
Schema-driven import. Every operation in the spec becomes a request; example bodies pre-fill where available. Request URLs start with {{baseUrl}}, a collection variable holding the first server (server variables applied). A relative server such as /api/v3 is resolved against the URL the spec was fetched from (remote-URL and desktop deep-link imports); from a local file it gets a placeholder origin and a warning. Multipart binary properties (format: binary, OAS 3.1 contentMediaType / contentEncoding, Swagger 2 type: file) import as file fields, and no boundary-less multipart Content-Type is added — the runtime sets it.
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. GraphQL bodies map to the query and variables editors (and back on export).
.http / .rest files
VS Code REST Client and JetBrains HTTP Client files: ###-separated requests, @name annotations and @var = value lines — at file level or inside a block before its request line — become requests and environment variables. JetBrains < {% %} / > {% %} script blocks are kept as pre-request and test scripts, with a warning in the import report because the JetBrains script API differs from rs.*.
HAR
Browser or proxy captures. You choose which entries to import in the review step (state-changing methods are flagged), and credentials in captured headers and bodies are redacted before they reach the review.
cURL
One POSIX-shell cURL command, from the cURL import card (paste it or pick a .sh / .txt file) or pasted straight into a request’s URL bar. Method, URL, headers, cookies, Basic auth, raw / form / binary bodies (including bash $'…' ANSI-C quoted strings, as Chrome DevTools “Copy as cURL” emits, and empty quoted arguments such as -d '') and settings such as -L, -k, --max-time and proxy options are filled in; unsupported options (such as --compressed, which the transports negotiate themselves) are shown as warnings. Shell expansions, substitutions and local-file reads are never evaluated.
Bodies follow curl’s own rules: -d / --data / --data-raw / --data-ascii are form-urlencoded unless a Content-Type says otherwise, --data-binary text is sent verbatim, --data-urlencode encodes per curl’s name=content rules, -G moves the data into the query string, and --json sets a JSON body with JSON Content-Type and Accept headers. -A (User-Agent), -e (Referer) and -b (Cookie) become headers, and every value-taking option consumes its value instead of being read as the URL (attached short forms, --flag=value and CRLF line continuations included). Query values are kept exactly as typed — a pasted %2B is not decoded to +.
Postman environments
*.postman_environment.json files import as environments. Numeric and boolean values are imported as strings (3 → "3"). Secret variables keep their value on desktop; in the browser the value is dropped and the import warnings list the keys to re-enter.
Remote URL
Fetch a collection or spec from a public HTTPS URL (no embedded credentials) and review it before anything is saved. The format is detected from the content; HAR is not accepted this way. Private, local and metadata addresses and binary responses are refused. On web and self-host the fetch goes through the backend’s /api/import/fetch route (10 MB cap, up to 5 redirects); on desktop it goes through the main process with the same URL and DNS checks.
OpenCollection
Native format — both the bundled YAML file and the directory layout. Round-trips HTTP, GraphQL, gRPC, SSE, and MCP requests with their auth, scripts, and folders — see the round-trip guarantees and known gaps.
Everything dropped or approximated is reported where the importer can see it, but a few cases are lossy:
Source
What happens
Insomnia v4
Only HTTP/GraphQL request resources are read. gRPC and WebSocket requests in the export are ignored. Items get fresh ids, so importing the same export twice never collides; a folder whose parent chain loops back to itself is placed at the root.
Insomnia v5
A node without children is treated as a request, so gRPC and WebSocket requests are imported as plain HTTP requests and won’t work as such.
Bruno .bru
grpc and ws request types import as HTTP requests, with a platform-unsupported warning naming each one. Multipart file rows import without their contents (named after the file, with a form-file warning) — re-pick the file. Bruno export writes a file row’s file name, never its bytes.
Postman
Unsupported auth (hawk, jwt, edgegrid, asap, azure, sasl, akamai) becomes no auth — see Postman import.
The desktop app accepts a reviewed restura://import link, for example
restura://import?url=https%3A%2F%2Fexample.com%2Fcollection.json&format=postman.
format is optional and may be postman, insomnia, openapi,
opencollection, hoppscotch, bruno, or http.
The link must point at a public URL without embedded credentials; the download
itself is HTTPS-only, so an http:// link opens the review but its download is
refused. Opening a link displays the source first and downloads nothing. Pick a
format if the link didn’t set one, then choose Download preview: Restura
fetches the source, and every redirect and target is checked by the normal URL
and DNS safety policy. The result goes through the usual import review, so
nothing is added until you confirm it. See Deep links
for the other restura:// routes.
OpenCollection (YAML) — the canonical export format. A single .yml file. See the round-trip guarantees for what is and isn’t preserved.
Postman v3 (folder / zip) — the default and recommended Postman export: Postman’s current YAML folder format. See Postman v3 export.
Postman v2.1 (single file · Newman) — one JSON file for Newman and other v2.1 tooling. See Postman v2.1 export.
Insomnia — for sharing with Insomnia users.
Bruno (.bru archive) — for sharing with Bruno users.
Exporting to a format that can’t hold everything in the collection tells you what was left out:
Format
How losses are reported
Postman v3 / v2.1
A structured export report listing every dropped or approximated item (for example, v2.1 has no item kind for gRPC, SSE, MCP, Kafka, MQTT or WebSocket). See Postman v3 export and Postman v2.1 export.
Insomnia
A warning toast. Non-HTTP requests are written as non-runnable stubs; request scripts, folder auth and scripts, collection auth, variables and scripts, and attached contract specs are left out. HTTP requests using auth Insomnia can’t carry (Digest, OAuth 1.0, NTLM, AWS Signature, WSSE) are exported without authentication, with an Insomnia export omits … auth warning.
OpenCollection
A warning toast if folders have contract attachments, which aren’t exported. Everything else round-trips (see below).
Bruno
A warning toast with the exporter’s first warning.
A toast shows the first warning and how many more there are ((+2 more)). Workflows are never part of a collection export; when the collection has any, every format shows a toast saying how many were not included.
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.
In OpenCollection exports, data the OpenCollection schema has no slot for — SSE/MCP requests, gRPC schema snapshots and timeouts, the desktop HTTP version preference, and a few auth options (OAuth 1.0a addParamsToBody, NTLM workstation, WSSE passwordType) — is stored in x-restura-* entries of the root extensions field so it round-trips; see Restura extensions. Postman, Insomnia, and Bruno exports keep only what those formats can express.
Pick a Postman v2.0 / v2.1 JSON file, a v3 folder (Import folder), a .zip, or a single v3 JSON/YAML file. The version is detected automatically and every format goes through the same parser the CLI uses.
Import report, no silent loss. Anything dropped or approximated is listed after import: unsupported auth, saved responses, item variables, extra events, file-body paths and similar. The raw Postman data is kept in a _postman sidecar in the Restura store (not in file-backed, Git-friendly collections, so it is lost when a desktop file collection is saved and reloaded; see ADR 0034).
Auth. OAuth 1.0a and NTLM map directly. Unsupported types (hawk, jwt, edgegrid, asap, azure, sasl, akamai) import as no auth with an unsupported-auth warning. The raw auth is kept in the _postman sidecar. v3 export restores it; v2.1 export restores only hawk and edgegrid, because jwt, asap, akamai, azure and sasl have no v2.1 type and are written as noauth and reported.
Variables. v2.x folder-level variables import as the folder’s variables (as in v3) and are written back by the v2.1 export; request-level variables stay in the sidecar. Path variables (url.variable, including v2.0 entries identified by id with no key) import as the request’s Path variables rows with :id kept in the URL, are substituted at send time, and are re-exported with a key.
Secret variables. v2.1 variables marked type: "secret" (off-schema, but Postman emits them) import value-less with a warning.
Environment files. In Postman (*.postman_environment.json) and Hoppscotch environment files, and Bruno environments (environments/*.bru in a Bruno import), secret variables keep their value on desktop, like a secret you type in. In the browser (web and self-host) the value is dropped, and the import warnings list the keys to re-enter. restura run --env also reads a Postman environment export (and --globals a globals export), using the values as they are.
Other kinds. v3 WebSocket and Socket.IO items import as native WebSocket / Socket.IO collection items (#1209); placeholder folders from older imports are upgraded automatically. LLM and data items become placeholder folders. MCP stdio items import as an empty placeholder folder named <name> (MCP stdio, disabled) with no request inside, so nothing can launch them. Restura keeps the program, option names and env variable names in the _postman sidecar, but never argument or env values; recreate the request and re-enter them before you connect. Vault (secret) variables import without a value.
Explicit No Auth. When a configured auth exists above an explicit Postman noauth, the import report gets an explicit-noauth entry, so restura run --strict-import exits 2. Export writes an explicit noauth (v2.1 and v3), never inherit, and markers on ancestors survive edits to child requests.
Request settings. v2.x protocolProfileBehavior and v3 settings are applied as Restura request settings: followRedirects, maxRedirects, strictSSL, followOriginalHttpMethod, followAuthorizationHeader, removeRefererHeaderOnRedirect, disableUrlEncoding, disableCookies, protocolVersion and TLS cipher options. Keys without a Restura equivalent (such as disableBodyPruning) are kept in the sidecar and reported.
Security downgrades such as strictSSL: false are called out as warnings.
Descriptions and scripts. Request and folder descriptions are kept (folder descriptions in the sidecar, for export). A disabled v2.x event is never run; it is kept for reference and exported again as disabled.
Other kinds, details. gRPC and MCP descriptions are kept for export (those Restura items have no description field). MQTT 5 message properties contentType, responseTopic and userProperties are imported and exported; other message properties are kept and reported. Form-data part content types are kept in v2.x and v3.
AWS Signature. A sessionToken (temporary STS credentials) is not applied by the Restura signer: the import report gets an awsv4-options entry, and both exports restore the token from the sidecar.
Limits. Archives up to 50 MB, with per-file, total, file-count and folder-depth limits; path traversal in archives is refused.
Web and self-hosted: downloads <name>.postman-v3.zip.
Desktop: writes <picked folder>/<name>/. If that folder is not empty Restura asks before replacing it, and replacing removes only Postman layout files, never other files you keep there.
Export report. Items v3 cannot hold are listed after export: a disabled v2.x script (v3 scripts are always active) is left out and reported as disabled-script; SSE requests are dropped, WSSE auth becomes no auth, secret variables are written with an empty value, Restura-only HTTP settings, GraphQL / gRPC extras, attached contract specs and folder variables are not exported, MCP Streamable HTTP is written as SSE, and some Kafka / MQTT broker options are left out.
Secrets follow the include-secrets prompt below.
Inherited auth. Requests that inherit their auth are exported as inherit, including after an import with “store secrets as handles” turned on.
WebSocket / Socket.IO. Native items are exported as v3 websocket-request / socket.io-request. Restura-only options (such as subprotocols, heartbeat, namespace and transports) are listed as websocket-extras / socketio-extras in the report. Credentials in the URL, query, headers and Socket.IO handshake auth are redacted.
Postman v2.1 (single file · Newman) writes one .json file.
Round trip. The export restores the _postman sidecar: saved responses / examples, protocolProfileBehavior, extra events and unsupported auth.
Auth. basic, bearer, apikey, oauth1, oauth2, digest, awsv4 and ntlm are exported. Inline auth secrets follow the include-secrets prompt below (excluded means blanked, included means written). Secret variables and keychain or other external secret handles are always exported empty.
Export report. Non-HTTP items (gRPC, SSE, MCP, Kafka, MQTT, WebSocket and Socket.IO) are reported in the export report and not exported, because v2.1 has no item kinds for them. GraphQL subscriptions are HTTP requests and are exported; only the subscription setting is dropped, reported as graphql-extras.
Auth credentials are redacted by default in collection exports. When a collection contains inline (plaintext) auth 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; in Insomnia and Bruno exports they become opaque {{handle:label}} placeholders, while both Postman formats write them empty and report them as secret-handle. Bruno exports include only the exported collection’s own environments, with secret values blanked; Postman exports always empty secret variables. When you exclude secrets, credential-named urlencoded and form-data text rows (client_secret, password, and so on) are counted by the prompt and blanked in every exporter: Postman v2.1 / v3, Insomnia, OpenCollection and Bruno, along with nested OAuth 2.0 values (client_assertion, code_verifier, assertion). Git-native desktop files are unchanged for now (#1234). Keychain handles found in sidecar auth are written empty and reported. The v2.1 export report also flags restored hidden scripts (restored-events) and local file paths (restored-file-path), because Newman may run or upload them. Always re-check an export before committing it to a public repo.
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.