Flatten a Financial API Response to CSV

A financial API response is a tree. A CSV is a flat table. The step in between is flattening, and it decides what your columns look like.

Open the API Response to Table

Open API Response to Table. Either enter the endpoint and your sign-in (Bearer token, API key in a header, or username and password) and click Send request, or paste the JSON you already have. If the response holds more than one list, pick the list that has your records.

Look at how the columns are named. Nested objects become columns named by their path, so a field company.sector inside each record gives a column called company.sector. Records that lack a field get an empty cell, so a column with many blanks usually means the field is optional. The Data Profiler counts them.

Download CSV. Each record is one row, which makes the file easy to load with a database COPY, a script or a spreadsheet. Keep tickers, ISINs and account ids as text so leading zeros are not lost, and check that amounts are numbers with the decimals you expect.

CSV stores no types, so the program that loads it must read dates and numbers itself. If you need the types kept, use the flat Parquet version instead, and if people will review the file, use the flat Excel version.

Everything runs in your browser and nothing is uploaded.

Open the API Response to Table

Related tool pages

  • JSON API Response to CSV: Turn the JSON from an API into a CSV file. Nested fields become columns and you pick which list to use. Free, in your browser, with an optional token.

How to use the API Response to Table: step by step

  1. Open API Response to Table.
  2. Send the request or paste the JSON.
  3. Pick the list and check the column names.
  4. Download CSV and profile it for blanks.

When to use the API Response to Table

  • Load an API response into a database
  • Check which fields a response always has
  • Share a flat file with an analyst
  • Keep a dated snapshot

Example

Input: GET https://api.example.com/users + Bearer token

Output: id,name,address.city 1,Ada,London

Frequently asked questions

How does the token work?

Choose Bearer token, API key in a header, or username and password, and paste the value. It is sent only to the API you call, kept in memory, and never saved or written to Data Lineage.

What if the API blocks the request?

Some APIs do not allow calls from other websites (CORS), so the browser blocks the request. Use an API that allows browser access, or ask its owner to enable CORS.

What happens to nested fields?

Nested objects are flattened into columns such as address.city. If the response has several lists, you can choose which one becomes the table.

Is it safe to use a token in API Response to Table?

Your token goes only to the API you call, straight from your browser. Data Utility never receives it or the response. It is kept in memory for that request, not saved, and not written to Data Lineage. Use a token with read-only access when you can.

Tip: Count blanks per column. A column that is mostly empty is an optional field.