Connector

Turn an API response into rows

APIs return nested JSON; analysis needs rows. The REST connector handles the part in between — authentication, pagination, and flattening the response into a dataset.

How it works

Authentication handled

Headers, tokens and keys belong to the connection, not to a script, and are not stored in the flow definition.

Pagination followed

The connector walks the pages rather than landing the first one and quietly stopping.

Nested responses flattened

Pick the collection inside the response and map its fields to columns, with the shape shown from a live sample.

Profiled like anything else

Once landed, an API dataset is indistinguishable from an uploaded file — same profile, same transforms, same lineage.

What happens after it lands

Once rows are in the catalogue, the connector that produced them stops mattering. The dataset is profiled, can be cleaned, modelled, put in a flow, governed and published exactly like every other dataset — which means switching how data arrives never means rebuilding what happens to it afterwards.

Questions about this connector

What authentication methods are supported?

Header-based schemes including bearer tokens and API keys, held on the connection and tested before it is saved.

What if the response shape changes?

The mapping is explicit, so a changed shape surfaces as an unmapped field at the next run rather than as silently missing data.

Can I call the API on a schedule?

Yes — put the connection in a flow and schedule the flow.

See it on your own data

DataLens is in private beta. Bring a file, a database or an API and work through the whole lifecycle in one sitting.

Request beta access