# HTTP Status & Uptime Checker — Bulk (`hipersoft/http-uptime-checker`) Actor

Check a batch of URLs for HTTP status, response time and up/down state, with expected-status rules. Cheap recurring availability monitoring without a full SaaS.

- **URL**: https://apify.com/hipersoft/http-uptime-checker.md
- **Developed by:** [hiper soft](https://apify.com/hipersoft) (community)
- **Categories:** Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.0005 / url checked

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## HTTP Status & Uptime Checker — Bulk

**Check a batch of URLs for HTTP status, response time and up/down state** — with expected-status rules. Cheap, recurring availability monitoring for all your endpoints without a full monitoring SaaS. Schedule it and get a report every run.

![HTTP Status & Uptime Checker input — configure the options in the Apify Console](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/http-uptime-checker-input.png)

### What it does

- Requests each URL and records **status code, response time and up/down**.
- Optional **expected status** (treat only that code as "up").
- Reports **content type, server, redirects** and the final URL.

### Use cases

- **Ops / SRE** — scheduled availability checks across many endpoints.
- **Agencies** — monitor client sites in bulk.
- **QA** — verify a list of URLs returns the expected status.

### Input

```json
{ "urls": ["https://apify.com", "https://api.yoursite.com/health"], "method": "GET", "expectedStatus": 0 }
```

| Field | Type | Description |
|---|---|---|
| `urls` | array | URLs to check. |
| `method` | string | `GET` or `HEAD`. |
| `expectedStatus` | integer | Only this exact status counts as up (0 = any 2xx/3xx). |
| `followRedirects` | boolean | Follow redirects. |
| `timeoutMs` | integer | Per-request timeout. |

### Output

![HTTP Status & Uptime Checker output — the results as a clean dataset](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/http-uptime-checker-output.png)

```json
{ "url": "https://apify.com", "status": 200, "responseMs": 180, "up": true, "finalUrl": "https://apify.com/", "checkedAt": "2026-08-18T00:00:00.000Z" }
```

#### Output schema

| Field | Type | Description |
|---|---|---|
| `url` | string (URL) | The URL checked. |
| `status` | integer | HTTP status code. |
| `responseMs` | integer | Response time in ms. |
| `up` | boolean | Whether the URL is up. |

### FAQ

**Can I get alerts?** Schedule it and use a webhook/integration to alert when `up` is false.

**Can I automate it?** Yes — via [integrations on the Apify platform](https://apify.com/integrations) and the [Apify API](https://docs.apify.com/api/v2).

### Notes

Original clean-room implementation.

# Actor input Schema

## `urls` (type: `array`):

URLs to check. One result row per URL with status, response time and up/down.

## `method` (type: `string`):

HEAD is lighter; GET is more compatible.

## `expectedStatus` (type: `integer`):

Treat only this exact status as 'up' (0 = any 2xx/3xx counts as up).

## `followRedirects` (type: `boolean`):

Follow redirects to the final destination.

## `timeoutMs` (type: `integer`):

Per-request timeout in milliseconds.

## Actor input object example

```json
{
  "urls": [
    "https://yoursite.com",
    "https://api.yoursite.com/health"
  ],
  "method": "GET",
  "expectedStatus": 0,
  "followRedirects": true,
  "timeoutMs": 20000
}
```

# Actor output Schema

## `results` (type: `string`):

The results as dataset items.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://apify.com",
        "https://example.com",
        "https://httpstat.us/503"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hipersoft/http-uptime-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [
        "https://apify.com",
        "https://example.com",
        "https://httpstat.us/503",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("hipersoft/http-uptime-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://apify.com",
    "https://example.com",
    "https://httpstat.us/503"
  ]
}' |
apify call hipersoft/http-uptime-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hipersoft/http-uptime-checker"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/IAEvjxx0E8EJjijmC/builds/gPQAjZed0CZZBglOf/openapi.json