A REST API for uptime monitoring, incidents, and status pages

Create and manage monitors from code, read status and uptime history, and keep incidents, status pages, and maintenance windows in sync with your deployments.

Start Free Request Demo

Monitors as code

Create, update, delete, pause, and resume monitors from scripts, infrastructure tooling, or your own admin panel.

Status and uptime history

Read current monitor status and historical uptime data to power internal dashboards and SLA reports.

Incidents and status pages

Manage incidents, status pages, maintenance windows, and alert channels without opening the dashboard.

What the PingRelay REST API covers

The PingRelay API exposes the same building blocks you use in the dashboard, so monitoring can be managed alongside the services it watches. Use it to keep monitor configuration consistent across environments, or to connect PingRelay to tools your team already runs.

Monitors: create, update, delete, pause, and resume website, API, TCP, port, SSL, keyword, page speed, and cron job monitors.
Status and history: read current monitor status and historical uptime data.
Incidents: manage incidents raised by your monitors.
Status pages: manage hosted status pages and the services they display.
Maintenance windows: schedule planned work so expected downtime does not trigger outage alerts.
Alert channels: manage the integrations that notify your team.

Authentication with API keys

Every request is authenticated with an API key passed as a bearer token in the Authorization header. Treat API keys like passwords: store them in a secrets manager or CI/CD variable, give each integration its own key, and rotate a key when the person or system using it changes.

Common ways teams use the API

Deployment pipelines: open a maintenance window or pause a monitor before a release, then resume monitoring when the deployment completes.
Infrastructure provisioning: create a monitor when a new service, customer environment, or domain goes live, and remove it when it is retired.
Reporting: pull uptime history into internal dashboards, client reports, or SLA reviews. Pair it with the uptime SLA calculator to translate percentages into allowed downtime.
Customer communication: update a status page or incident from the tools your support and operations teams already use.

If you would rather work with monitoring data in an AI assistant, the PingRelay MCP server is included on the same plans.

Plans that include API access

Pro ($29/month): REST API and MCP access, 50 monitors, 30-second checks from 10 regions, 25 status pages, and 5 teammates with role-based access.
Business ($79/month): REST API and MCP access, 250 monitors, 30-second checks from 17 regions, 100 status pages, 15 teammates, SSO, and audit logs.

Compare every limit on the pricing page, or read the PingRelay documentation for endpoint details.

Frequently asked questions

The REST API is included on the Pro ($29/month) and Business ($79/month) plans. Free and Starter accounts use the PingRelay dashboard.

Requests are authenticated with an API key sent as a bearer token in the Authorization header. Keep keys in a secrets manager or CI variable rather than in source code.

You can create, update, delete, pause, and resume monitors; read monitor status and uptime history; and manage incidents, status pages, maintenance windows, and alert channels.

Yes. A deployment job can call the API to open a maintenance window or pause a monitor before a release, then resume monitoring once the deployment finishes.

Automate your uptime monitoring with the PingRelay API

The REST API is included on Pro and Business, alongside 30-second checks, teammates, and role-based access.

Start Monitoring Free View Pricing