Integration · APIs

REST API to CSV or database integration

An HTTP source reads an API endpoint, follows its paging and remembers where it stopped. The rows then go to a file, a destination or a table.

REST API (HTTP source) → CSV file or database table

What you need

Modules. Transfer for the source and Flow for the schedule. Add Database for the table load, which together is the Everything bundle.

Edition. DataBridge Server for unattended schedules.

Pricing and what each edition includes.

Limits, stated plainly
  • Redirects are not followed, and only the status codes you accept count as success.
  • Request headers are never sent over plain http. Use https for anything that carries a token.
  • The page limit is a hard stop, default 20 pages and at most 500, so a paging mistake cannot become an endless crawl.

A real DataBridge screen, with sample data from a demo instance.

Steps

How it works.

Each step names the feature as it appears in the product.

  1. Step 1

    HTTP source

    Enter the URL and method. GET reads, and POST suits search or GraphQL endpoints. Put tokens or API keys in the request headers.

  2. Step 2

    Records path

    Say where the array of records sits in the response, for example data.items.

  3. Step 3

    Paging and incremental

    Page by number, offset, cursor or Link header, with a hard page limit. A {watermark} placeholder in the URL fetches only what changed since the last successful run.

  4. Step 4

    File template and mapping

    Check the rows against a template and map them to the shape you need.

  5. Step 5

    Deliver or load

    Push CSV to a destination, or use Write to database to load an existing table.

Questions

Common questions.

Can it fetch only new records?

Yes. Put {watermark} in the URL, for example ?updated_since={watermark}, and each run asks only for what changed since the last successful fetch.

Does it handle paged APIs?

Yes. Page number, offset, cursor in the response body and Link header paging are supported, with a page size and a page limit.

Keep reading

Related use cases and integrations.

QuickBooks, Sage 100, NetSuite, Salesforce, HubSpot, Dynamics 365, Shopify and Amazon are trademarks of their respective owners. Names are used only to say which system a connection, layout or file is for. ExtensibilityCo is not affiliated with or endorsed by any of them.

Next step

Try the parts that are free today.

The free browser edition needs no sign-in and never uploads your files.