REST API Fetcher & Paginator — Any JSON API to Dataset

Fetch any JSON REST API into an Apify dataset — extract the items array by dot-path and auto-follow pagination (page, offset, cursor, or next-link). Custom headers for auth. Turns any API into a dataset.

Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.

What you get

Returns one clean, structured row per result. Every row reports its own status so you never get a silent blank.

How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or schedule it to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

Input

{
  "url": "https://hn.algolia.com/api/v1/search?query=apify",
  "itemsPath": "hits",
  "paginationStrategy": "none",
  "headers": {},
  "maxPages": 20,
  "maxItems": 100000
}

Sample output

[
{
  "result": "example",
  "status": "ok",
  "scrapedAt": "2026-09-03T09:00:00.000Z"
}
]

Typical uses

• Pull a paginated public/partner API into a dataset without writing code.
• Feed the output into the Notion/Airtable/Sheets exporters or the format converter.
• Snapshot an API on a schedule.

Pricing

$0.50 / 1,000 results ($0.0005 per result), plus a near-zero start fee. You are never charged beyond your limit, and blocked or failed items are reported honestly — not billed as data.

FAQ & limitations

• Public data only — no login walls, no cookies required.
• Rate limits on the source may require the proxy or a retry on very large pulls.
• Every row reports its own status, so partial results are always labeled, never faked.
• Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
• Formats: results export as JSON, CSV, Excel, or HTML from the dataset.

Related actors

• Portfolio Health Monitor
• Format Converter
• URL Metadata Extractor

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• REST API Fetcher & Paginator — Any JSON API to Dataset returns the upstream endpoint's rows unchanged, so its output follows the source's own shape rather than a schema imposed by the Actor.
• REST API Fetcher & Paginator needs no API key, login or account of any kind before its first run.
• Every one of REST API Fetcher & Paginator's 9 inputs is optional, so it runs with no configuration at all.
• Every number published about REST API Fetcher & Paginator is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• REST API Fetcher & Paginator is filed under developer tools and automation so that it is found by the people looking for that job, not by its internal name.

Limitations

• REST API Fetcher & Paginator reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.