Skip to main content
Postchi can import collections exported from Postman. You can import a single collection as a .json file, or import an entire workspace as a .zip archive. You can also import an open api spec either as .json or .yaml file. Postchi converts each request into a .chttp file and recreates your folder structure.
If you have an open api spec you can add it as a source so you can always stay in sync with it’s changes.

​
How to import

1

Open the Import menu in Postchi

From the file menu select Import
2

Choose import type

Select One time import
3

Choose your file

Drag your file in the drop zone or Select the file you exported from Postman or an open api spec. Postchi detects the format automatically and imports everything immediately.
4

Review the imported collection

Postchi creates a folder in your requests directory named after the collection. Inside, each request becomes a .chttp file, preserving the original folder structure.

​
What gets imported

​
What doesn’t get imported

Some Postman features don’t have a direct equivalent in Postchi. You’ll need to recreate these manually after import.
Pre-request and test scripts are not imported. Postman scripts use the Postman sandbox API, which is not compatible with Postchi. Rewrite any logic you need as Postchi before or after scripts.
  • Postman environments — as of version 0.7.2 environments do not get imported, we will add this feature soon.

​
After import

Once your collection is imported, review the generated .chttp files and:
If your Postman collection used collection-level auth, configure it in Postchi using the Folder Settings. Every request in the folder will then inherit the auth automatically.