Service Status & Incident API API
The Service Status & Incident API returns live up/down status and incident data for hundreds of vendors as clean JSON.
🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.
The primary status endpoint returns a vendor's name, indicator, operational flag, description, active-incident count and last-updated time, and you can pull incidents, components, a summary, check multiple vendors at once, batch and list supported vendors. It is built for monitoring dashboards, incident tooling and reliability workflows that need normalized status-page data without polling each vendor's page. One ReefAPI key, one shared credit pool, the standard { ok, data, meta, error } envelope.
Real request and response JSON
Captured from the indexed primary action, status, on .
{
"method": "POST",
"url": "https://api.reefapi.com/status-intel/v1/status",
"headers": {
"x-api-key": "$REEF_KEY",
"content-type": "application/json"
},
"body": {
"vendor": "github"
}
}{
"ok": true,
"meta": {
"api": "status-intel",
"endpoint": "status",
"mode": "live",
"latency_ms": 711.3,
"record_count": 1,
"bytes": 4310,
"cache_hit": false,
"method": "public_status_api",
"vendor": "github",
"platform": "statuspage"
},
"data": {
"vendor": "github",
"name": "GitHub",
"kind": "statuspage",
"platform": "statuspage",
"generic": false,
"category": "dev-tools",
"indicator": "operational",
"raw_indicator": "none",
"description": "All Systems Operational",
"is_operational": true,
"updated_at": "[redacted-phone]T15:54:09.347Z",
"active_incident_count": 0,
"source_url": "https://www.githubstatus.com/api/v2/summary.json"
}
}What the Service Status & Incident API API does
| Action | Description | Concrete use case | Key params |
|---|---|---|---|
| status | Current OVERALL status for a vendor → normalized indicator (operational/degraded/partial_outage/major_outage/maintenance) + is_operational boolean + description. | Ops teams call status to get current OVERALL status for a vendor → normalized indicator (operational/degraded/partial_outa…. | vendor |
| incidents | Recent or active incidents for a vendor (title, impact, status, timeline of updates, affected components). active_only=true → just the ongoing ones. | Developer tools call incidents to get recent or active incidents for a vendor (title, impact, status, timeline of updates, affected…. | vendor, active_only, limit |
| components | Per-component (sub-service) health for a vendor — which specific products are degraded. | Validation workflows call components to get per-component (sub-service) health for a vendor. | vendor, limit |
| summary | Full one-call snapshot for a vendor: overall status + components + active incidents + scheduled maintenances (the whole status page in one normalized object). | Data-quality teams call summary to get full one-call snapshot for a vendor. | vendor |
| check_multi | THE dashboard call: give your stack as a list (keys / brands / domains / status hosts) → each is auto-resolved to its real status page and its LIVE status is returned, read from the SOURCE. 'Are any of my dependencies down right now?' Per-item errors never fail the whole call. | Ops teams call check_multi to get tHE dashboard call. | vendors |
| batch | Alias of check_multi — overall status for a batch of vendors in one call (up to 25). | Developer tools call batch to get alias of check_multi. | vendors |
| list_vendors | The supported vendor set (key → name, kind, category, status host). Optionally filtered by category. Also lists explicitly-unsupported vendors (e.g. Azure) with the reason. | Validation workflows call list_vendors to get the supported vendor set (key → name, kind, category, status host). | category |
Call status from your stack
curl -X POST https://api.reefapi.com/status-intel/v1/status \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"vendor":"github"}'import requests
r = requests.post(
"https://api.reefapi.com/status-intel/v1/status",
headers={"x-api-key": REEF_KEY},
json={
"vendor": "github"
},
)
print(r.json()["data"])const res = await fetch("https://api.reefapi.com/status-intel/v1/status", {
method: "POST",
headers: {
"x-api-key": process.env.REEF_KEY,
"content-type": "application/json",
},
body: JSON.stringify({
"vendor": "github"
}),
});
const { ok, data, meta, error } = await res.json();Ask your MCP-connected assistant: call reefapi.status-intel.status with {"vendor":"github"}.Who uses this API and why
- Monitoring dashboards call check_multi to show the live status of every SaaS a company depends on.
- Incident tooling uses incidents to alert when a critical vendor reports an outage.
- Reliability teams use summary and components to track a vendor's uptime history over time.
Questions developers ask before integrating
What is the Service Status & Incident API API?
Service Status & Incident API API is a ReefAPI endpoint group for service status & incident api It returns live JSON through POST requests under /status-intel/v1.
Is the Service Status & Incident API API free to try?
Yes. ReefAPI starts with 1,000 free credits, no card required. Service Status & Incident API calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Service Status & Incident API login or account?
No login to Service Status & Incident API is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Service Status & Incident API data?
The page example is captured from a live status call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Service Status & Incident API API use?
Service Status & Incident API actions currently cost 1 credit per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.
Can I call Service Status & Incident API from an AI assistant or MCP client?
Yes. Connect ReefAPI once through MCP and your assistant can call status-intel actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Service Status & Incident API API a Service Status & Incident API scraper?
It is the managed alternative to a DIY Service Status & Incident API scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same service status & incident api back as clean JSON.
Why does my Service Status & Incident API scraper keep getting blocked?
Most Service Status & Incident API scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked or failed calls are free.