Importing
Everything imports from the Import menu on the Collections page and in the API Client. Nothing is sent anywhere: files are read on your computer.
What you can import
| Source | What you get |
|---|---|
| OpenAPI spec (3.x, YAML or JSON) | A collection with one request per operation, or the endpoints of a mock service. OpenAPI 3.2’s query operations are included. |
| Postman file (collection v2.0 or v2.1, environment or globals) | A collection or variables. Credentials go to the encrypted store, not to a file. |
| Browser recording (HAR) | Requests from the calls you made in a browser. Save the Network tab as a HAR file, choose it, and pick the calls: API calls are selected for you, pages and files are one click away, and repeated calls count as one. |
| cURL command | One request, from ⋯ More actions in the API Client. |
From a HAR file, tokens, passwords and API keys become secret variables whose values go to the Vault, never to a file, and cookies are left out. The responses can be kept too, so the result can become a mock service that answers the way the real API did.
Mock services from a spec
Open a mock service and choose Import OpenAPI. Zyvra reads the spec, shows every operation, and creates an endpoint for each one you tick, with example responses taken from the spec.
When the spec changes
Import the new version into the same service. Routes that are already there are marked, and you choose what happens to them:
- Leave them as they are (the default).
- Add the responses they are missing: only responses the endpoint does not have yet (and a description, if it has none) are added. Your rules, faults, edited responses and the active scenario are not touched.
Routes the new spec dropped are listed but never deleted. Delete them yourself if the API really removed them.
Export
Collections, environments and globals export as Postman files (Export on a collection, or zyvra export postman). Secret values are never exported.