Integrations
Connect realuptime to what you already run
Every integration below is live today: alerting channels alongside Slack and operator email, a badge and embed for your status page, and programmatic access through the REST API, the MCP server, and a GitHub Action for CI.
Alerting
Webhook notifications
A signed HTTPS callback on every down and recovery transition, alongside Slack and operator email. HMAC-SHA256 signed, retried with backoff, no tier gate.
Alerting
PagerDuty
Paste your Events API v2 routing key and realuptime opens and resolves PagerDuty incidents automatically as a monitor goes down and recovers.
Status page
Status page badge and embed
A live uptime badge (SVG) and an embeddable status card (iframe) for any public status page, generated from the dashboard.
API
REST API
List, create, update, and delete monitors, read status pages and incidents, all over plain HTTPS with a bearer API key. Growth and Scale plans.
API
MCP server
The same seven operations as the REST API, exposed as MCP tools so Claude or any other MCP client can check and manage your monitors directly.
CI
GitHub Action
Drop a step into any workflow to check one or more monitors' current status and fail the run (or just report outputs) before or after a deploy.
Alerting channels
Slack and operator email ship on every plan. Webhook notifications and PagerDuty are a third and fourth channel on top of those two, configured from the dashboard's Notifications section, with no tier gate. All four channels fire on the same down and recovery transitions and respect the same scheduled-maintenance suppression. See the API reference for the webhook payload shape, signature verification, and PagerDuty's event mapping.
Status page badge and embed
Every status page can generate a live uptime badge (an SVG image) and an embeddable status card (an iframe) from the dashboard, ready to drop into a README, a docs site, or your own homepage. Both reflect the same real-time status your public status page shows.
Programmatic access
The REST API and the MCP server expose the same six operations against the same data: list and create monitors, read a monitor's live status, update which regions probe it, remove it, list your status pages, and list recent incidents. Both are gated to Growth and Scale plans, authenticated with the same bearer API key, generated from the dashboard's API & MCP access section. Read the full API reference or the MCP server docs for setup, authentication, permission scopes, and rate limits.
GitHub Action
A composite GitHub Action wraps the REST API's read endpoints into a single workflow step: check one or more monitors and fail the run (or just report outputs) if any of them is down or degraded. Useful as a post-deploy gate, or anywhere a workflow needs to confirm a dependency is actually healthy before continuing. See the GitHub Action docs for setup and every input and output.