Pricing

from $0.35 / 1,000 requests

Try for free

Go to Apify Store

HTTP Request Runner

Try for free

Send many HTTP requests to public web addresses and APIs in one run: GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS with your own headers and body. Each request gives one row with status, headers, body, parsed JSON, redirect chain and timing. Secret field for API keys.

Pricing

from $0.35 / 1,000 requests

Rating

0.0

(0)

Developer

Sanira Botheju

Actor stats

Bookmarked

Total users

Monthly active users

a day ago

Last modified

Configure MCP server with HTTP Request Runner: Bulk GET, POST and API Calls

The configuration above connects to the hosted Apify MCP server with the HTTP Request Runner: Bulk GET, POST and API Calls Actor already loaded. It uses OAuth, so your client opens a browser window to sign you in to Apify on first use. No API token is needed. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.

Get a ready-to-use configuration for your MCP client with the HTTP Request Runner: Bulk GET, POST and API Calls Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,cyber1nj3ct0r/http-request-runner.

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.

HTTP Request — Bulk & Proxied API Calls

memo23/http-request

Send HTTP requests (GET, POST, PUT, PATCH, DELETE) to any API with custom headers, params and body. Send a whole batch in one run instead of one run per call, route through Apify proxies by country, and forward each response to a callback URL. Built for Clay, n8n and no-code stacks.

Muhamed Didovic

238

5.0

(1)

Batch Runner

useful-tools/batch-runner

Actor for starting several Runs from single Input. It also has capability to merge the Dataset items from the created batch.

Useful tools

5.0

(1)

HTTP Request

parsebird/http-request-actor

Send HTTP requests (GET, POST, PUT, PATCH, DELETE) to any API endpoint with customizable headers, parameters, and body data. Forward responses via callback URL. Perfect for Clay users and no-code API integrations.

ParseBird

202

5.0

(1)

HTTP Request Scraper — Bulk URLs, No Charge For Blocks

thenetaji/http-request-scraper

Send GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS to any public URL and get back the status, headers, cookies and full body. Runs through managed datacenter and residential proxies behind a real browser TLS fingerprint, rotating that identity on every retry. Blocked URLs are never charged.

The Netaji

HTTP Request Runner: Single or Bulk API Calls with curl Import

getascraper/http-request-runner

Send one API call or thousands per run. Paste curl commands, fill URL templates from your rows, follow pagination, retry safely and extract JSON fields. Works with Clay, n8n, Make and Zapier. Private and cloud-metadata addresses are always blocked, so agents can use it safely.

GetAScraper

Restore failed requests

onidivo/restore-failed-requests

Restore failed requests of a run from the dataset to the request queue.

Onidivo Technologies

HTTP Request Runner — Bulk & Proxied

seemuapps/http-request-runner

Send hundreds of GET, POST, PUT or DELETE requests through datacenter or residential proxies and get status, headers, body and timing per URL.

Seemu Scraping

Selenium Cloud Runner

sovanza.inc/selenium-cloud-runner

Selenium Cloud Runner scrapes JavaScript-heavy websites using Selenium and headless Chrome. It extracts data with CSS or XPath rules, supports scrolling, popup handling, screenshots, proxies, retries, and structured dataset exports.

Sovanza

HTTP Request Builder

maximedupre/http-request-builder

Build requests for public HTTP or HTTPS endpoints with methods, headers, query parameters, bodies, and expected status codes. Paste cURL commands or submit a batch, then get one result row per request with the status, final URL, response content, timing, and outcome.