Bulk HTTP Status & Redirect Audit API

Check public URLs for HTTP errors, redirect chains and HTTPS downgrades. Source-backed results without browser overhead.

What you can do

Validate URLs exported from a sitemap, CMS migration or marketing spreadsheet.

Quick start

{
  "urls": [
    "https://example.com/"
  ],
  "maxItems": 10
}

Run the Actor and download the default dataset as JSON, CSV or Excel. Inspect the OUTPUT key-value-store record before treating the run as complete. Live example sources can change or become unavailable.

Behavior and limitations

Each input URL is checked independently with a GET request; response bodies are not downloaded. The result includes every HTTP redirect, final status and HTTPS-to-HTTP downgrade detection. A 404 or 500 is a successful HTTP observation and produces a billable row with isBroken=true. DNS, TLS, robots or timeout failures are uncharged source errors in OUTPUT. Redirects are capped at five. It does not discover links from pages or execute JavaScript redirects. Availability is an observation at the recorded time, not a continuous uptime guarantee.

Every result preserves its source URL and an observedAt UTC timestamp. Network or parsing errors are listed by source in OUTPUT.errors; other successful sources still return results. OUTPUT.warnings, complete and status distinguish a full observation from partial output. If every requested source fails, the run fails rather than silently returning an empty success.

Pricing

USD 2 per 1,000 successful URL audit rows ($0.002 per row), plus a $0.005 Actor-start event for the default 256 MB run. No result event is charged for a failed source. The Actor-start event can still apply to a failed run. Higher memory can increase start-event quantity according to Apify's rules. This description must match the currently effective Store pricing; check the pricing tab before running. Apify charges only as configured there.

Resource and access limits

At most 1,000 output rows; public ports 80/443 only; five redirects; 2 MiB decoded body per request; approximately 100 seconds for fetching. Requests are sequential with no retries, CAPTCHA bypass, credentials, residential proxies or paid upstream APIs. robots.txt is respected; missing robots.txt (404/410) allows fetching, while blocked or unavailable policies produce errors. Public DNS addresses are validated and pinned for each connection. Use only sources you are permitted to access and respect source terms. Private networks and URLs with embedded credentials are rejected.

API and automation

Call POST https://api.apify.com/v2/actors/soilair~bulk-http-redirect-audit-api/runs with the example JSON and your own Apify authorization header. Poll the returned run ID, then fetch /v2/datasets/{defaultDatasetId}/items. Schedule subsequent runs in Apify Console; pass earlier keys/hashes explicitly where supported. The Actor never schedules jobs itself.

Data handling and support

Input and results remain in your Apify run's storage under the platform's retention settings. The Actor sends requests only to the input sources, their public redirects and robots.txt. No separate analytics or customer-data endpoint is used. Do not put secrets or private customer URLs in the input. Developed with AI assistance and tested with deterministic fixtures plus public-source smoke checks; this does not guarantee all storefronts or websites will work. For support, send the run ID, source URL and expected behavior via the Apify issue tab without credentials.