Export a REST API into one Apify Dataset using page-number, offset, cursor or next-link pagination. Set page and item limits, then check the run summary to see whether the export finished or stopped early.
2026-09-26: More reliable requests and spending checks
Fixes
Spending checks and billing receipts use the effective event prices supplied for your run, including discounts and zero-priced events.
Compressed HTTP responses are limited while they are decoded, so a small compressed download cannot expand past the response limit in memory.
Retry-After is treated as the server's minimum wait. If it exceeds the retry budget, the request ends with an explicit failure instead of retrying early.
Request logs and error messages mask credentials. Cookies received from a server are not automatically reused on later requests.
Invalid headers and excessively deep, non-finite or otherwise invalid JSON return explicit errors. DNS resolution is included in the attempt timeout. An unresolved hostname is reported as SOURCE_FAILED, not invalid input.
If storage fails after part of a page was delivered, RUN_SUMMARY preserves the confirmed item count. An unconfirmed charge is marked unknown and is not replayed.
2026-09-19: Export every page of one REST API
Changes
0.1
Give one request and a page, offset, cursor or next-link pattern. Each non-empty page is stored as it arrives. The run summary says whether the export finished, was empty, hit your limit, detected a pagination loop, or stopped on a source failure.
A non-empty page costs $0.002, plus the $0.01 start. The two-page demo is $0.014. Set maxPages, maxItems and maxTotalChargeUsd before a larger export.
This is the first published version, so there is no previous input to migrate.
