Export a collection to file#

Export takes a collection out of API Client as a file you can share or keep as a backup. It is the counterpart to importing: a colleague can import what you export. You can also save a single response to disk.

Export a collection#

Open the menu on a collection in the Collections tree and choose Export. API Client writes the collection as a Postman version 2.1 file and downloads it, named after the collection. There is no prompt. It is one click.

The file carries the collection's folders, requests, bodies, and collection variables. It also carries the auth types that have a Postman equivalent, such as bearer token, basic auth, and API key. Two things stay behind: flows, which have no Postman counterpart, and auth types with no clean equivalent. API Client leaves those out rather than export them wrongly.

Note Export is a snapshot taken at the moment you click. To keep files on disk that stay in step as you edit, use Linking to a folder instead.

Save one response to a file#

You can also save a single response from the response panel with its download button. A save window opens with a suggested filename. The name comes from the response's own filename header where it sets one, or from its content type. API Client writes a binary response as raw bytes, and anything else as text. This is the quick way to keep a downloaded file or set aside a payload for later.