Clicking through a dashboard is fine for ten monitors. For a hundred services, dozens of client sites or infrastructure that changes every week, monitoring has to live in code. The Uptimecheck REST API covers the same resources as the dashboard.
Resources
monitors: HTTP(S), ping and port checks.dns-monitors: record monitoring with change history.servers: server resource monitoring.heartbeats: cron job and scheduled task monitoring.domains: registration expiry tracking.notification-handlers: email, Slack, Discord, Telegram, Microsoft Teams and webhooks.status-pages: create and configure status pages.statistics: uptime and response time data, including status page statistics.
Create a monitor from your pipeline
Authenticate with a bearer token and send a request:
curl --request POST --url https://app.uptimecheck.com/api/monitors --header 'Authorization: Bearer {api_key}' --form 'name=Checkout' --form 'target=https://northwind.shop/checkout'
Run it in the same step that deploys the service, and every new endpoint is monitored the moment it goes live. The full reference is in the documentation.
Common uses
Agencies
Onboard a new client in one script: create a project, add monitors for the site and checkout, add the domain and a branded status page. Offboarding is the same script in reverse.
Platform teams
Keep monitors in sync with your service catalogue. When a service is added in infrastructure code, a monitor and a heartbeat follow.
Reporting
Pull statistics into your own dashboards, invoices or monthly client reports. Exports to CSV, JSON and PDF are also available in the app.
Webhooks for the other direction
The API lets you manage Uptimecheck. Webhooks let Uptimecheck call you: post every incident to your own endpoint and connect it to whatever runs your on-call process. See alerts and notifications.
Practical tips
- Store the API key as a secret in your CI system, never in the repository.
- Make scripts idempotent: look up a monitor by name or target before creating it, so a re-run does not create duplicates.
- Use the same naming scheme in the API as in your infrastructure, so a monitor is easy to trace back to the service it watches.
- Pull statistics on a schedule rather than on every page view of your own dashboard.
Most teams start by scripting the boring part, adding monitors for new client sites or services, and expand from there to reporting and status pages.
Statistics for your own reports
The statistics endpoints return uptime and response time data for your monitors, and visit data for your status pages. Agencies use them to build branded monthly reports; product teams pull them into the same dashboard as their business metrics. Either way, the numbers come from the same checks that send your alerts.
Rate your scripts kindly: fetch what you need on a schedule, cache it, and keep the API key out of logs.
API access is included on Professional and Business. Compare plans on the pricing page, and see API monitoring to monitor your own API with Uptimecheck.