Skip to content
Json Works

Postman Tips: Exporting Responses and Collections

Updated

Postman is built for sending requests, so getting data out of it is not always obvious. Whether you want one response in a spreadsheet, a record of every request in a collection, or an automated export from a run, there is a way. These are the techniques worth knowing.

Export a single response

Copy the body

In the response panel, select the Body tab, choose Pretty or Raw, and use the copy icon at the top right. Pretty is easier to read if you paste it somewhere; Raw is smaller and just as valid JSON.

Paste the result into JSON to Table to get a sortable table, then export CSV or Excel. The full walkthrough is in how to convert Postman JSON to CSV.

Save the response to a file

Use Save Response above the response body and choose Save to a file. This is the safer route for large responses, because the preview may truncate long bodies. Drop the saved file straight onto the table tool.

Save as an example

Save Response > Save as example stores a response inside the request in your collection. Examples travel with the exported collection, so they are a good way to document what an API returns. They also power Postman’s mock servers.

Export a whole collection

To share or back up a collection, use the three-dot menu beside it and choose Export. Select Collection v2.1 unless you have a reason to use an older version, and save the .json file.

An exported collection is a single JSON file containing every folder, request, example and script. It is easy to read in principle and tedious in practice, because requests are nested in folders and the details live several levels deep.

See a collection as a table

Open the exported file in the Postman Collection Viewer. It shows one row per request with the method, URL, headers, authentication and test scripts, and you can filter, sort and export to CSV or Excel. That is useful for:

  • API audits. Which endpoints use which auth type? Which requests have no tests?
  • Documentation. A spreadsheet of endpoints and methods is a quick inventory.
  • Reviews. Spot duplicate or inconsistent URLs across folders.
  • Migration. List everything before moving to another tool.

Exported collections can contain secrets such as API keys, tokens and passwords stored in headers or variables. A client-side viewer keeps the file on your device, but remember to redact before sharing the export with anyone.

Environments

Environments export separately: open Environments, use the three-dot menu and choose Export. Keep secrets out of shared environments by using the “current value” field, which is not synced or exported by default, for sensitive values.

Capture data automatically with scripts

For repeatable extraction, use scripts in the Post-response tab (formerly Tests). A few useful snippets:

Save one value for the next request:

const body = pm.response.json();
pm.environment.set("token", body.access_token);

Log the response in the console (open it with Ctrl+Alt+C or the Console button) so you can copy it from there:

console.log(JSON.stringify(pm.response.json(), null, 2));

Collect results across a collection run. Variables can accumulate data as each request runs:

const rows = JSON.parse(pm.collectionVariables.get("rows") || "[]");
rows.push({ id: pm.response.json().id, status: pm.response.code });
pm.collectionVariables.set("rows", JSON.stringify(rows));

After the run, copy the rows variable and paste it into the table tool.

Use the Collection Runner with data files

The Collection Runner can iterate a request over a CSV or JSON file, for example one request per user ID. After the run, Export Results saves a JSON report of every request, status and test result. That file works well in a table: sort by status code to find failures, or filter for tests that did not pass.

Newman: export from the command line

Newman is Postman’s command-line runner. It suits CI jobs and large exports:

npm install -g newman
newman run collection.json -e environment.json \
  --reporters cli,json --reporter-json-export results.json

The results.json file is the same structure as the runner export. Open it in a table to review hundreds of requests at once.

Convert between Postman and cURL

To share one request with someone who does not use Postman, use Code (the </> icon on the right) to generate a cURL command, or import a cURL command using Import > Raw text. If you need the same request in fetch, Axios or Python, paste the cURL into the cURL Converter. See cURL to fetch, Axios and Python.

Troubleshooting

The body looks truncated. Postman limits preview size for very large responses. Save the response to a file.

Pasted JSON fails to parse. You may have copied the Visualize or Preview tab, or HTML from an error page. Make sure the Body tab is selected. See common JSON errors.

Variables like {{baseUrl}} appear in the exported URLs. Collections store variables, not resolved values. That is expected; the viewer shows the template.

Numbers look different after export. Large integer IDs beyond 15 digits can be rounded by spreadsheets. Export to .xlsx, or import CSV with the column set to Text. Details are in JSON to Excel.

A suggested workflow

  1. Send the request, check the response, Save Response to a file if it is large.
  2. Drop it into the table viewer, hide noise columns, sort and filter.
  3. Export CSV or Excel for sharing.
  4. Export the collection periodically and review it as a table for audits.
  5. Automate with Newman when you need the same export repeatedly.

More guides

All guides · FAQ