Copy API JSON Results into Excel or Google Sheets Columns

Check the shape of your JSON first

The easiest input is an array of objects with the same keys, like a list of orders or users. Each object becomes a row and each key becomes a column header. If your response wraps that list in an outer object (for instance {"data": [...]}), paste only the inner array.

From response to spreadsheet

1. Copy the JSON from your API client, browser network tab or terminal.
2. Paste it into the converter, or open the file directly if you saved it.
3. Check the output: the first line should be the headers and each later line one record.
4. Copy the TSV output.
5. Click cell A1 in Excel or Google Sheets and paste. The values fill columns without any import wizard.
6. Save the sheet in your normal format, or export as CSV if another tool needs it.

Why TSV beats CSV for pasting

Commas appear inside names, addresses and descriptions, which is exactly why CSV needs quoting rules. Tab characters almost never appear in ordinary text, so tab-separated output is safer to paste. It also avoids a regional problem: in several European locales Excel expects semicolons instead of commas, so pasted CSV lands in a single column, while tabs work everywhere.

Things that trip people up

• Nested objects become extra columns with dotted names such as address.city, and lists of objects appear as JSON text inside a cell. Remove what you do not need first.
• Long numbers such as 16-digit IDs may be shown in scientific notation by Excel. Format the column as Text before pasting if you need them intact.
• Leading zeros in values like 00123 can be dropped by a spreadsheet that treats them as numbers. Format as Text first.
• Values that look like dates, such as 3-4, may be converted automatically. Check anything date-like after pasting.
• If records have different keys, check that the header row includes every field you need.

Make the output repeatable

If you do this weekly, write down the steps: which endpoint, which fields, and in what order the columns should appear. Keep a header template in your sheet so you always paste data below the same labels. When the API adds a new field, the converted output will gain a column, so check that formulas which refer to column letters still point at the right data. Referring to columns by header name, for example with lookup formulas, survives such changes better than fixed letters.

For very large responses, split the work. Spreadsheets have row limits and slow down with tens of thousands of lines, so filter the API request by date or page and paste each batch separately.

A quick sanity check

After pasting, compare the row count with the number of items in the JSON. If your API returned 250 records, the sheet should have 250 data rows plus one header row. Spot check two or three rows against the original, particularly values that contain quotes or line breaks, since those are the most likely to shift.

Because the conversion runs in your browser, you can paste real response data without uploading it to a server, which is convenient when the data includes customer details. Still follow your company policy about where that data may be stored once it is in a spreadsheet.