Steadyline Data
Home / Tools / HTTP Request Runner
Developer tools

Bulk HTTP Request Runner & API Scraper: 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.

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.

Use cases

  • Bulk API calls without code: call a REST API for thousands of IDs from a URL template and variables.
  • Paginated API exports: follow Link headers, cursors or page/offset until the end, with JSONPath extraction.
  • HTML to Markdown for LLMs: fetch pages and get clean Markdown.
  • Uptime and status checks: scheduled checks of endpoints with retries and status/latency in the output.
  • No-code glue: a reliable HTTP step for Zapier/Make/n8n flows that need retries and rate limits.

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).

Use it from AI agents, the API or no-code tools

Add Apify's hosted MCP server with just this tool:

{
  "mcpServers": {
    "http-request-runner": { "url": "https://mcp.apify.com?tools=steadyline/http-request-runner" }
  }
}

Sign in with Apify (OAuth) on first connect, or send an Authorization: Bearer <APIFY_TOKEN> header. Then ask your agent, for example:

Use steadyline/http-request-runner to fetch these 30 URLs, convert each page to Markdown and return the titles.

See MCP setup for Claude, Cursor and VS Code or add all tools at once.

REST API

Run it and get results in one call:

curl -X POST "https://api.apify.com/v2/acts/steadyline~http-request-runner/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"requests": [{"id": "crawlee-issues", "url": "https://api.github.com/repos/apify/crawlee/issues", "query": {"per_page": "5", "state": "all"}, "headers": {"Accept": "application/vnd.github+json"}}, {"id": "example-page", "url": "https://example.com/"}], "pagination": {"type": "linkHeader", "maxPages": 2}, "extract": {"titles": "$[*].title", "numbers": "$[*].number"}}'

No-code

Use the official Apify app in Zapier ("Run Actor"), Make ("Run an Actor") or n8n (Apify node), choose steadyline/http-request-runner, then send the dataset items to Google Sheets, Slack, a CRM or a database.

Pricing

Pay per event on Apify, no subscription. Prices are read from the public Apify Store listing; the Store page is authoritative.

EventPricePer 1,000
Request
Charged per successful HTTP request.
$0.0008$0.80
Actor start (Apify standard)
Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
$0.00005–

FAQ

Are my API keys safe?

Auth fields are secret inputs (encrypted by Apify), and the Actor redacts them from output, including keys echoed back in response bodies.

Does it render JavaScript?

No, it is a plain HTTP client. For rendered pages, use a browser-based Actor; for screenshots see Website Screenshot.

What does it cost?

$0.0008 per request or page fetched, so $0.80 per 1,000.

Can I run it on a schedule?

Yes. Create an Apify Schedule (or a saved Task with a schedule) and connect a webhook or integration to receive results.

Need a feature or found a bug?

Open an issue on the Issues tab of the tool's Apify Store page or email hello@steadylinedata.com. Built and maintained by Steadyline Data.

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.