REST API Market Data to Clean, Flat JSON

Market data APIs often wrap the prices in metadata and nested objects. A flat JSON list is easier to feed to a chart, script or app.

Open the API Response to Table

Open API Response to Table, enter the endpoint and your sign-in, and click Send request. Pick the list that holds the bars. Nested fields are flattened into fields named by their path, such as quote.close, and the wrapper around the list is dropped.

JSON is a list of records, each with named fields. Numbers and true/false stay as such when type detection is on, but ids and codes with leading zeros should stay text. Choose pretty JSON to read it, or compact JSON to save space. Download JSON when the table looks right.

Compare the number of records with what the API documentation says you should get, because a page limit can cut a long history. Only GET requests over https work, and an API that blocks browser calls is refused.

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 and send the request.
  2. Pick the list that holds the bars.
  3. Check the columns.
  4. Download JSON and compare the record count.

When to use the API Response to Table

  • Give a chart a flat list of prices
  • Strip the wrapper from an API response
  • Save a snapshot of a response
  • Prepare test fixtures from real data

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: Compare the record count with the API documentation. A page limit can silently cut the list.