Import and export

Switching API clients should not mean losing years of work. Echo imports from the tools you probably use today, and it never locks your data in.

Import from Postman

Echo imports Postman collections and environments, both of them, with full round-trip fidelity. Your folder structure, requests and variables arrive intact, and you can export back to Postman formats at any time. Trying Echo is not a one-way door.

  1. Export your collections and environments from Postman.
  2. Import the files into Echo.
  3. Check that your requests resolve against the imported environments, then carry on working.

Import from Insomnia and Bruno

Coming from Insomnia or Bruno works the same way: export from your current tool and import into Echo. Your requests land in collections you can immediately reorganize with the tools described in /docs/echo/collections-and-sharing.

Import an OpenAPI 3 spec

Feed Echo an OpenAPI 3 document, JSON or YAML, and it builds requests from the spec with automatic request-type inference, so operations come in as the right kind of request instead of a pile of generic stubs. This is the fastest way to start exploring an API you have a contract for but have never called.

Import a cURL command

Paste a cURL command and Echo turns it into a proper request. Handy for the commands that live in bug reports, API docs and terminal history. If your organization has Pro AI seats, there is also an AI-assisted cURL import for the messier cases, see /docs/echo/ai-features.

Export your work

Export collections to Postman formats or OpenAPI 3.1 JSON. OpenAPI gives you a specification you can use in other API tools, while Postman exports keep your existing collection workflow available.

Keep a collection in a folder

Link a collection to a folder to keep its requests and environments as readable JSON files alongside your project. You can review changes with your usual tools and add the files to version control.

Echo shows whether changes came from the app, the folder or both. Choose import or export to apply them; linking a folder does not commit or push anything to Git. Secret values stay out of the exported files. Use variable references for credentials and review files before sharing them.

Publish API docs to DocuVault

Docs export publishes a collection as Markdown API documentation into Gapfy DocuVault. Instead of a wiki page that drifts out of date, your team's document space gets docs generated from the collection you actually run.

  1. Pick the collection you want to document.
  2. Run the docs export.
  3. Find the generated Markdown API docs in DocuVault, ready to share with your team.

With a paid Echo plan and the required permissions, publish documentation from a synced collection and copy its public link. You can publish an updated version, rotate the link or revoke the publication. Anyone who has the public link can read it, so review the content before sharing it. This publication is separate from exporting Markdown to DocuVault.

Next steps

  • Organize what you imported: /docs/echo/collections-and-sharing
  • Wire imported requests to environments: /docs/echo/environments-and-variables