Postchi can import collections exported from Postman. You can import a single collection as aDocumentation Index
Fetch the complete documentation index at: https://docs.getpostchi.com/llms.txt
Use this file to discover all available pages before exploring further.
.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.
How to import
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.
What gets imported
| Item | How it maps in Postchi |
|---|---|
| Requests | Converted to .chttp files with method, URL, headers, and body |
| Folder structure | Recreated as nested folders inside requests/ |
| Request names | Used as the .chttp file name |
| Basic and Bearer auth | Converted to basicAuth(<username>,<password>) and bearer(<token>) in the Authorization header |
Postman variables ({{variable}}) | Converted to Postchi variables (<variable>) |
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.- 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: