How does it find the records inside a wrapped response?

It looks for the record array under common wrapper keys - data, results, items, records, rows, entries, payload, hits, and others - and turns that array into rows. If the records live one level deeper, such as data.items, that envelope is unwrapped too. Pagination fields sitting next to the array (page, total, next) are ignored for the row set.

Does pagination metadata end up in my spreadsheet?

No. When the response is a wrapper object, only the detected record array becomes rows. Sibling scalars and objects like page, per_page, total, or links are skipped, so you get a clean table of records rather than a one-row blob of metadata.

What happens to nested resources like a customer object?

In the default Separate columns mode, a nested resource flattens into dotted columns such as customer.name and customer.address.city, which you can filter and pivot. Switch to JSON in one cell to keep a whole sub-resource as JSON text instead.

Can I convert a paginated endpoint with many pages?

Each request returns one page. Combine the pages into a single array first, or convert each page and stack the resulting sheets in Excel. For large payloads, most APIs accept a fields parameter so you can trim columns before exporting.

Is it safe to convert a response that contains tokens or emails?

Yes. Conversion runs entirely in your browser, so a response with access tokens, emails, or customer data never leaves your device and is never uploaded to a server.

How to Convert an API Response (JSON) to Excel

Last updated: 13 June 2026

REST APIs almost never return a bare list. They wrap the records in an envelope - a data or results key, pagination counters around it, and nested resources inside each record. This guide shows how the converter looks past that envelope and turns the actual records into a clean spreadsheet, free, with no signup, and processed entirely in your browser.

A realistic wrapped response

A typical paginated endpoint returns something like this - a record array under results, with page metadata as siblings:

{
  "page": 1,
  "per_page": 2,
  "total": 137,
  "results": [
    { "id": 101, "customer": { "name": "Ada", "city": "London" }, "total": 49.5 },
    { "id": 102, "customer": { "name": "Linus", "city": "Helsinki" }, "total": 12.0 }
  ]
}

The records array is detected automatically

You don't have to strip the wrapper. The converter scans for the main record array - common keys include data, results, items, records, and others - finds results here, and turns its two objects into two rows. The page, per_page, and total fields are pagination noise, so they are left out of the table entirely.

Some APIs nest the list one level down, for example { "status": "ok", "data": { "items": [ … ], "pagination": { … } } }. That envelope is unwrapped too - the converter steps into data, finds items, and uses it as the rows.

Nested resources become dotted columns

Each record above has a nested customer resource. In the default Separate columns mode it spreads into customer.name and customer.city, sitting beside id and total. The total values 49.5 and 12.0 stay real numbers you can sum. For responses with several nesting levels, the nested JSON to Excel guide goes deeper, and the JSON array to Excel guide breaks down the row-and-column mapping once the array is found.

Tips for clean API output

Keep long IDs (order IDs, user IDs) as quoted strings in the JSON so they aren't rounded - the converter is big-number-safe and preserves them either way.
For paginated endpoints, combine the pages into one array, or convert each page and stack the sheets in Excel.
Large response? Filter fields at the API (most support a fields parameter) before exporting.
Coming from Postman specifically? The Postman JSON to Excel guide covers saving the response first.

Step-by-step

Copy the JSON response from your API client, browser, or terminal (or save it as a .json file).
Open the converter and paste the JSON or drop the file (up to 15 MB).
Preview the first rows to confirm the columns look right.
Click Download Excel and open the .xlsx in Excel, Google Sheets, or LibreOffice.

Frequently asked questions

How does it find the records inside a wrapped response?: It looks for the record array under common wrapper keys - data, results, items, records, rows, entries, payload, hits, and others - and turns that array into rows. If the records live one level deeper, such as data.items, that envelope is unwrapped too. Pagination fields sitting next to the array (page, total, next) are ignored for the row set.
Does pagination metadata end up in my spreadsheet?: No. When the response is a wrapper object, only the detected record array becomes rows. Sibling scalars and objects like page, per_page, total, or links are skipped, so you get a clean table of records rather than a one-row blob of metadata.
What happens to nested resources like a customer object?: In the default Separate columns mode, a nested resource flattens into dotted columns such as customer.name and customer.address.city, which you can filter and pivot. Switch to JSON in one cell to keep a whole sub-resource as JSON text instead.
Can I convert a paginated endpoint with many pages?: Each request returns one page. Combine the pages into a single array first, or convert each page and stack the resulting sheets in Excel. For large payloads, most APIs accept a fields parameter so you can trim columns before exporting.
Is it safe to convert a response that contains tokens or emails?: Yes. Conversion runs entirely in your browser, so a response with access tokens, emails, or customer data never leaves your device and is never uploaded to a server.

Related guides

See all guides or the FAQ.

Convert your API response to Excel →