JSON Records Path Finder

Almost no API returns a bare array. The rows you want are nested somewhere inside an envelope — under data, results, items, records, or something bespoke — alongside paging and status fields. The records path is the dot path to that array, for example data.items. Every tool that reads a REST API needs to be told it.

It walks the whole response, finds every array of objects, and ranks them by how much they look like a result set: how many rows they hold, how consistent the keys are across those rows, and how shallow the path is. An array of three objects with identical keys beats a deeply nested array of one.

Because that is what they become in a table. An object like customer: { name, email } cannot occupy one spreadsheet cell usefully, so it is flattened to customer.name and customer.email. The preview shows exactly the columns you would get.

They are marked rather than flattened. A row containing a list — line items on an order, tags on a post — is really a second table, and flattening it into numbered columns produces something nobody can query. Pull it as its own job with its own records path.

No. It cannot even fetch a URL for you: browsers block cross-origin requests to most APIs, and pretending otherwise would mean proxying your credentials through a server. Paste the response you already have — parsing happens in the page.