Export and share
Git-backed YAML workspaces
Section titled “Git-backed YAML workspaces”For team sharing, prefer Kurlo’s Git/YAML storage over repeated JSON exports. It stores workspace state as plain YAML files:
kurlo.ymlandworkspaces/**/*.ymlare shared.- Sensitive values become
{{kurloSecret:...}}placeholders; the real values remain in Kurlo’s encrypted local profile outside the repository. - Folder hierarchy is represented by
request.folderPathpluscollection.folderPaths, so empty folders survive round-trips.
See Kurlo YAML format for the public contract.
All-data backups
Section titled “All-data backups”Use Settings -> General -> Data -> Export all data for a Kurlo-to-Kurlo profile backup. Unlike collection interchange formats, it includes history, cookies, all local workspaces, and selected preferences.
The file is plaintext and can contain secrets. Import replaces the current local profile rather than merging it. See Backup & recovery for the exact contents, exclusions, recovery-key behavior, and a safe restore procedure.
Export
Section titled “Export”Open the collection’s ⋯ menu and choose Export…. The picker offers Postman v2.1 JSON and v3 YAML, Insomnia Export v4 JSON, OpenAPI 3.0 JSON, Swagger 2.0 JSON, and OpenCollection YAML.
Choose Postman collection v3 (YAML folder) to transfer native gRPC requests into Postman Desktop. The v2.1 option writes a single JSON file for Postman’s file importer. See protocol support by format for the full list.
Secrets marked as secret are stripped, redacted, or kept as Kurlo secret placeholders depending on the target format. Git/YAML workspaces keep the real values in Kurlo’s encrypted local profile, outside shared files.
Sharing within a team
Section titled “Sharing within a team”For day-to-day collaboration:
- Use Git-backed YAML workspace storage.
- Commit
kurlo.yml,.gitignore, andworkspaces/**/*.yml. - Keep
{{kurloSecret:...}}placeholders intact; Kurlo resolves them from each user’s encrypted local profile. - Use import/export formats only for interoperability with another client.
For environment-specific variables, keep non-secret defaults in the workspace and put real secret values in local secrets.