Bulk HTTP Request Runner: retries, pagination & JSONPath avatar

Bulk HTTP Request Runner: retries, pagination & JSONPath

Pricing

from $0.80 / 1,000 requests

Go to Apify Store
Bulk HTTP Request Runner: retries, pagination & JSONPath

Bulk HTTP Request Runner: retries, pagination & JSONPath

Run thousands of HTTP/API requests from a list or a template: auth (bearer, basic, API key), per-host rate limits, retries with Retry-After, pagination (Link header, cursor, page/offset), JSONPath/JMESPath extraction and HTML-to-Markdown. Secrets are never echoed. By Steadyline Data.

Pricing

from $0.80 / 1,000 requests

Rating

0.0

(0)

Developer

Steadyline Data

Steadyline Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Bulk HTTP Request Runner: retries, pagination & JSONPath extraction

Run anything from a few to 100,000 HTTP/API requests from a plain list or from one template plus a list of variables. You get clean, structured results: status, the useful response headers, timing, the parsed JSON, values extracted with JSONPath or JMESPath, and HTML converted to Markdown. Retries, per-host rate limits and pagination are handled for you. Your credentials never appear in the output.

Use it for API backfills, enrichment jobs, health checks, polling endpoints, feeding LLM pipelines with Markdown, or any "call this URL for every row in my spreadsheet" task, without writing or hosting code.

Features

  • Two ways to define requests: a requests list (method, url, headers, query, body), or a template with {{placeholders}} plus variables. A placeholder that is the whole value keeps its type, so numbers stay numbers in JSON bodies.
  • Authentication: Bearer, Basic, or an API-key header. These are entered in secret input fields, which the platform stores encrypted.
  • Secrets are never echoed:
    • Values from the authentication fields are removed from URLs, headers, bodies, extracted values and Markdown.
    • Authorization and cookie headers, and headers or query parameters with names like token, key, secret or signature, show as [redacted].
  • Politeness built in: overall concurrency (hard cap 20) and requests per second per host (hard cap 10/s).
  • Retries: on network errors, 408, 425, 429 and 5xx, up to 5 times. Retry-After is honored (capped at 120 s). Otherwise backoff is exponential with jitter.
  • Pagination:
    • linkHeader (GitHub style rel="next")
    • jsonCursor (a cursor value or next URL at a JSONPath)
    • page and offset parameters
    • maxPages up to 1000, with itemsPath to stop on an empty page
  • Parsing: automatic JSON detection, extract rules (JSONPath or JMESPath), and an HTML→Markdown option that keeps main or article content and drops nav, scripts and footers. Raw body storage can be turned off, and maxBodyBytes caps the body size (hard cap 10 MB).

Output (one row per request or page)

id, pageIndex, request (method, redacted URL, redacted headers, hasBody), status, ok, finalUrl, durationMs, attempts, headers (content-type, link, retry-after, rate-limit headers, etag, and others), contentType, bodyBytes, bodyTruncated, extracted, json or body, markdown, error.

Output sample

Real output from a test run (GitHub issues with Link-header pagination and JMESPath [].title / [].number, plus example.com converted to Markdown). The json field is shortened here:

[
{
"id": "gh-issues",
"pageIndex": 0,
"request": {
"method": "GET",
"url": "https://api.github.com/repos/apify/crawlee/issues?per_page=3&state=all",
"headers": {
"accept": "application/vnd.github+json"
},
"hasBody": false
},
"status": 200,
"ok": true,
"finalUrl": "https://api.github.com/repos/apify/crawlee/issues?per_page=3&state=all",
"durationMs": 368,
"attempts": 1,
"headers": {
"content-type": "application/json; charset=utf-8",
"content-length": "2695",
"content-encoding": "gzip",
"link": "<https://api.github.com/repositories/66670819/issues?per_page=3&state=all&after=Y3Vyc29yOnYyOpLPAAABoYhLpAjPAAAAAWvFpZs%3D&page=2>; rel=\"next\"",
"etag": "W/\"63eb12b0f4552d4469152ba3669f405daf6267d6f23ee575fa6d9c7a5bb7a816\"",
"cache-control": "public, max-age=60, s-maxage=60",
"x-ratelimit-limit": "60",
"x-ratelimit-remaining": "51",
"x-ratelimit-reset": "1793339689"
},
"contentType": "application/json; charset=utf-8",
"bodyBytes": 14343,
"bodyTruncated": false,
"extracted": {
"titles": [
"fix(http)!: verify TLS certificates by default",
"test(basic-crawler): pin that minConcurrency tasks keep running under overload",
"`npx crawlee create` templates are broken"
],
"numbers": [
4317,
4316,
4315
]
},
"json": "[… 3 issue objects, omitted here …]",
"body": null,
"markdown": null,
"error": null
},
{
"id": "html-md",
"pageIndex": 0,
"request": {
"method": "GET",
"url": "https://example.com/",
"headers": {},
"hasBody": false
},
"status": 200,
"ok": true,
"finalUrl": "https://example.com/",
"durationMs": 66,
"attempts": 1,
"headers": {
"content-type": "text/html; charset=utf-8",
"content-encoding": "br",
"last-modified": "Thu, 29 Oct 2026 13:15:03 GMT"
},
"contentType": "text/html; charset=utf-8",
"bodyBytes": 577,
"bodyTruncated": false,
"extracted": null,
"json": null,
"body": null,
"markdown": "This domain is for use in documentation examples without needing permission. This is not a service; avoid relying on it for testing and monitoring purposes.",
"error": null
}
]

Pricing (pay per event)

EventPrice
request: one successful response (2xx/3xx, or a code you list in allowedStatusCodes); each pagination page counts as one$0.0008

Failures are never charged. Network errors, timeouts, 4xx/5xx after all retries, and invalid URLs are stored with an error but cost nothing. Retries of a request that finally succeeds count as one request. Cost example: 10,000 API lookups via a template, with 2 pages each = 20,000 successful requests × $0.0008 = $16.

Acceptable use

This tool sends the requests you define, so you are responsible for them. Only call APIs and websites you are allowed to use. Follow their terms of service, authentication rules and published rate limits. Do not use it for denial of service, load or stress testing of systems you don't own, credential stuffing, or getting around access controls. Concurrency and per-host rate have hard caps to prevent abuse. Don't send personal data you have no lawful basis to process. We may stop runs that break these rules.

Made by Steadyline Data.