# Statuspage Incident Digest (Multi-page, Pay-per-event) (`harry-smart/statuspage-incident-digest`) Actor

Monitor many vendor status pages at once. Fetches incidents from the public Atlassian Statuspage API (/api/v2/incidents.json) for every URL you give and returns one clean row per incident.

- **URL**: https://apify.com/harry-smart/statuspage-incident-digest.md
- **Developed by:** [Harry Smart](https://apify.com/harry-smart) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 page checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Statuspage Incident Digest

**Monitor dozens of vendor status pages in one run.** Give this Actor a list of public status pages powered by Atlassian Statuspage (GitHub, OpenAI, Atlassian, Cloudflare, Discord, Dropbox, Twilio and thousands more) and it returns one clean, normalized row per incident: name, status, impact, start and resolution time, duration, affected components and a permanent link.

No browser, no proxies, no login. The Actor only reads the official public JSON endpoint every Statuspage site exposes (`/api/v2/incidents.json`), so runs are fast, cheap and reliable.

### Who is it for?

- **SRE / DevOps teams** who want one feed of upstream outages for every SaaS dependency.
- **IT procurement and vendor-risk teams** comparing vendor reliability (incident counts, impact, time-to-resolve).
- **MSPs and agencies** reporting third-party incidents to clients.
- **AI agents and automations** that need a structured "is vendor X having problems right now?" signal.

### How it works

1. You enter status page URLs, e.g. `https://www.githubstatus.com` or just `status.openai.com`. Any path is ignored; only the origin is used.
2. For each page the Actor calls `{origin}/api/v2/incidents.json` (the ~50 most recent incidents).
3. Optional filters are applied (`since`, `onlyUnresolved`, `maxItems`).
4. Each incident is saved to the dataset. A run summary is stored in the key-value store under `SUMMARY`.

Pages that fail (not a Statuspage site, DNS error, timeout) are logged and listed in `SUMMARY.failures`; they are **never charged**.

### Input

| Field | Type | Description |
|---|---|---|
| `pageUrls` | array of strings (required) | Public Statuspage URLs. |
| `maxItems` | integer, 1–50 (default 50) | Max incidents per page. |
| `since` | ISO date (optional) | Skip incidents that started before this, e.g. `2026-10-01`. |
| `onlyUnresolved` | boolean | Only incidents that are still open. |
| `includeUpdates` | boolean | Attach the full update timeline (status + message). |

```json
{
  "pageUrls": ["https://www.githubstatus.com", "https://status.openai.com"],
  "maxItems": 20,
  "since": "2026-10-01"
}
```

### Output

```json
{
  "id": "93njd414rpbx",
  "name": "Incident with Actions, Pull Requests and Issues",
  "status": "resolved",
  "impact": "minor",
  "started_at": "2026-10-12T12:21:47.965Z",
  "resolved_at": "2026-10-12T20:16:07.447Z",
  "duration_minutes": 474,
  "is_resolved": true,
  "components": ["Issues", "Pull Requests", "Actions"],
  "shortlink": "https://stspg.io/flldq0dn2wdz",
  "page": "GitHub",
  "page_url": "https://www.githubstatus.com",
  "source_url": "https://www.githubstatus.com/api/v2/incidents.json"
}
```

Export as JSON, CSV, Excel or via the Apify API, or connect it to Slack, Zapier, Make or webhooks.

### Pricing (pay per event)

You only pay for results:

- **Actor start** – small flat fee per run.
- **Status page checked** – per page successfully fetched.
- **Incident returned** – per incident row written to the dataset.

Set a maximum cost per run in the run options; the Actor stops cleanly when the limit is reached. Tip: use `since` or `onlyUnresolved` on scheduled runs to pay only for new incidents.

### Scheduling tip

Create a Schedule (e.g. every 15 minutes) with `onlyUnresolved: true` and a webhook or Slack integration to get alerted when any of your vendors has an open incident.

### FAQ

**Which sites work?** Any status page hosted on Atlassian Statuspage (most have a "Powered by Atlassian Statuspage" footer). Custom-built status pages are not supported.

**Why only ~50 incidents?** That is what the public endpoint returns. Schedule the Actor to build your own history.

**Is this legal?** The Actor reads only public, unauthenticated JSON that status pages publish for exactly this purpose. It does not log in, bypass protections or collect personal data.

**Something broke?** Open an issue on the Actor's Issues tab and include the page URL.

# Actor input Schema

## `pageUrls` (type: `array`):

Public Atlassian Statuspage sites, e.g. https://www.githubstatus.com. Any path is ignored; only the origin is used.

## `maxItems` (type: `integer`):

Maximum incidents to output per status page (the public API returns up to ~50 most recent).

## `since` (type: `string`):

Optional ISO date/time (e.g. 2026-10-01 or 2026-10-01T00:00:00Z). Incidents that started before this are skipped.

## `onlyUnresolved` (type: `boolean`):

Output only incidents that are not resolved/postmortem yet.

## `includeUpdates` (type: `boolean`):

Attach the incident update timeline (status + message) to each row.

## Actor input object example

```json
{
  "pageUrls": [
    "https://www.githubstatus.com"
  ],
  "maxItems": 50,
  "onlyUnresolved": false,
  "includeUpdates": false
}
```

# Actor output Schema

## `incidents` (type: `string`):

One row per incident plus an optional SUMMARY row.

# 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 = {
    "pageUrls": [
        "https://www.githubstatus.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("harry-smart/statuspage-incident-digest").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 = { "pageUrls": ["https://www.githubstatus.com"] }

# Run the Actor and wait for it to finish
run = client.actor("harry-smart/statuspage-incident-digest").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 '{
  "pageUrls": [
    "https://www.githubstatus.com"
  ]
}' |
apify call harry-smart/statuspage-incident-digest --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,harry-smart/statuspage-incident-digest"
        }
    }
}
```

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/9MESZBnPyjBos4wzY/builds/WJHmkOUzdaVnoFmMD/openapi.json