Skip to content
Download

Import and export by protocol

Check which request types can move between tools.

FormatImport into KurloExport from Kurlo
Postman v3 Native Git folderHTTP, GraphQL, gRPC, WebSocket, Socket.IO, and MCP over HTTPHTTP, GraphQL, and native gRPC. SSE as HTTP streaming
Postman v2 JSONv2.0 and v2.1. HTTP and GraphQL, with additional request metadata in files exported by Kurlov2.1 JSON. HTTP, GraphQL and SSE using HTTP fields. Kurlo can reconstruct gRPC, WebSocket, and Socket.IO from its own export metadata
Insomnia v4 JSONHTTP, GraphQL, gRPC, WebSocket, and Socket.IOv4 workspace JSON, including gRPC, WebSocket and Socket.IO request resources
OpenAPI / SwaggerHTTP and SSE operationsHTTP and SSE as OpenAPI 3.0 or Swagger 2.0
Bruno / OpenCollectionHTTP, GraphQL, gRPC, WebSocket, and Socket.IOOpenCollection YAML with HTTP, GraphQL, gRPC, WebSocket, and Socket.IO request records
Kurlo all-data backupAll Kurlo request typesAll Kurlo request types
Kurlo Git/YAML workspaceAll Kurlo request typesAll Kurlo request types

Use Postman v3 to move native gRPC requests between Kurlo and Postman. Kurlo can import a v3 folder or a single *.request.yaml file. The v2.1 JSON export stores gRPC-specific fields in x-kurlo for re-import into Kurlo.

A Postman v3, OpenAPI, or Swagger export reports how many requests it skipped. Use a Kurlo workspace or backup to preserve Kurlo-specific fields across every request type.