API Response to Table: Tokens, API Keys and CORS Errors

Most problems turning an API response into a table are about how you sign in or what the browser allows. Here is what to check.

Open the API Response to Table

Short answer: in API Response to Table you enter an https address, choose how the API checks who you are, and send one GET request from your browser. If the response is JSON, you get a table you can download as CSV, Excel, JSON or Parquet. When it fails, the cause is usually the sign-in method, a CORS rule or a redirect.

Pick the right sign-in method

  • Bearer token: for APIs that expect Authorization: Bearer your-token.
  • API key in a header: for APIs that want a header such as X-API-Key. Enter the header name and the key.
  • Username and password: for APIs that use basic sign-in. Enter user:password.
  • None: for public APIs. Use Try a public example to see how it works.
  • Extra headers: add any other header your API requires, such as an account or version header.

What happens to your token

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

Fixing the common errors

  • "Enter a full address that starts with https://": the address must be complete. Plain http addresses are not allowed.
  • "The browser could not reach this API": the most common cause is CORS. Some APIs do not allow calls from other websites, and the browser blocks the response. Ask the API owner to allow it, or export the data from the API's own dashboard and open the file instead.
  • A redirect message: the API sent you to another address. For safety your token is not sent along. Use the final address instead.
  • A timeout: the request waits up to 30 seconds. A slow API or a very large response may not finish.
  • A 401 or 403 answer: check the token, the header name and whether the token has read access.

Choosing the list that becomes the table

If the response holds several lists, such as users and orders, choose which one becomes the table. Nested fields become columns such as address.city, so detail is kept.

Limits

  • It makes one GET request. It does not page through results, so for a paged API enter the address of each page you need.
  • Only https addresses are supported.
  • The API must allow browser calls (CORS).

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.

Also try

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

  1. Open API Response to Table.
  2. Enter the https address.
  3. Choose the sign-in method and paste the token or key.
  4. Send the request and download the table.

When to use the API Response to Table

  • Export users or orders from a SaaS API to Excel
  • Check what an API returns as a table
  • Debug a token or header problem
  • Prepare API data for a spreadsheet

Example

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

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

Frequently asked questions

Why does my API call fail in the browser but work in curl?

Browsers enforce CORS, so an API must allow calls from other websites. curl does not enforce it.

Is my token saved?

No. It is kept in memory for the request and never saved or written to Data Lineage.

Does it follow pagination?

No. It makes one GET request. Enter the address of each page you need.

Can I use http addresses?

No. Only https addresses are supported.

Which download formats are available?

CSV, Excel, JSON and Parquet.

Tip: A CORS message means the API blocks browser calls, not that your token is wrong.