
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.
REST API Fetcher & Paginator — Any JSON API to Dataset returns 4 documented output fields, including value, status, message and rowsReturned. Every field carries a declared type, a written description and an example value. 843 runs are recorded on Apify.
- 4
- Output fields
- 9
- Inputs
- 843
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| value | number | The measured value for this row. Units are in the README and sometimes in a sibling field. | 42.5 |
| status | string | Outcome recorded for this row. | active |
| message | string | Human-readable note about this row or the run. | Add your API key to classify answers. No text was sent anywhere. |
| rowsReturned | number | How many rows the run returned. Zero on a blocked run, which is a real value and the entire point of such a record. | 0 |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"value": 42.5,
"status": "active",
"message": "Add your API key to classify answers. No text was sent anywhere.",
"rowsReturned": 0
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| url | stringrequired | The JSON API endpoint (include query params). |
| itemsPath | stringoptional | Dot-path to the array in the response, e.g. data.results or hits. Empty = response is the array. |
| paginationStrategy | stringoptional | none, page, offset, cursor, or link. |
| paginationParam | stringoptional | Query param for page/offset/cursor (e.g. page, offset, cursor). |
| cursorPath | stringoptional | For cursor/link: dot-path to the cursor value or next URL in the response (e.g. meta.next). |
| pageSize | integeroptional | For offset strategy: how much to advance each page. |
| headers | objectoptional | Extra request headers, e.g. {"Authorization":"Bearer ..."}. |
| maxPages | integeroptional | Stop after N pages. |
| maxItems | integeroptional | Hard cap. |
04 — run
Run REST API Fetcher & Paginator on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
4 of 4 fields described
- What does REST API Fetcher & Paginator — Any JSON API to Dataset return?
- It returns 4 documented output fields: value, status, message and rowsReturned. Each field declares its type, a description of what it holds, and an example value.
- What input does REST API Fetcher & Paginator — Any JSON API to Dataset require?
- url is required. A further 8 inputs are optional. The full input schema, with types and defaults, is below.
- Does REST API Fetcher & Paginator — Any JSON API to Dataset need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run REST API Fetcher & Paginator — Any JSON API to Dataset?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.