Skip to content
Restura Docs

OpenCollection

OpenCollection is an open specification for API collections — designed for portability between tools, version control, and CI. Restura uses it as its native format for export.

Why an open format

Section titled “Why an open format”

Postman’s format is locked. Insomnia’s is locked. Bruno’s is its own. Switching tools means a lossy migration every time. OpenCollection exists to be the format you can move into and out of without losing fidelity.

What it covers

Section titled “What it covers”
  • Requests across all protocols Restura supports: HTTP, GraphQL, gRPC, WebSocket, Socket.IO, SSE, Kafka, MCP.
  • Nested folders with inherited auth, headers, and variables.
  • Environments with scoped variables.
  • Scripts (pre-request and test) — sandbox-portable JavaScript.
  • Workflows — request sequences with extraction and retries.
  • Auth schemes — every scheme in the auth guide, with secrets stored as references (SecretRef).
  • Vendor extensions via the extensions field — so tools can persist proprietary data while staying spec-compliant.

Two layouts

Section titled “Two layouts”
  • Bundled JSON — a single .json file. Easy to drop into another tool.
  • Directory layout — one file per request, in a folder structure that mirrors your collection tree. Friendly for git.

Restura exports both; import auto-detects.

Round-trip guarantees

Section titled “Round-trip guarantees”

Importing a Restura-exported OpenCollection back into Restura is lossless. Importing a Postman v2.1 collection into Restura and exporting as OpenCollection retains every Postman-supported field; round-tripping back to Postman is best-effort (some Restura-specific features may not have Postman equivalents).

Section titled “Related”
Restura The API client that speaks every protocol.
Built by Dipjyoti Metia GitHub MIT licensed