API monitoring that fits how you build
PingInsight monitors APIs and infrastructure at the layer you actually run: HTTP/API with assertions, ping, TCP, UDP, DNS, SSL, domain, mail, SSH, NTP, and inbound heartbeat checks — as often as every second, and fully driven by a documented REST API and on-demand revalidation.
Assertions, not just 200s
A 200 OK can still be wrong. Validate the status code, response body and JSON, headers, and response time, so a deploy that returns the right code with a broken payload — or one that's quietly slow — still pages you instead of looking healthy.
Everything as code
Click-ops doesn't belong in your deploy pipeline. Manage monitors, status pages, and alert channels through the same documented REST API the dashboard uses, with scoped API keys, plus on-demand revalidation and an SSE stream for real-time status in your own tools.
Beyond HTTP
Real systems aren't only web servers. Check TCP and UDP ports, DNS records, SSL-certificate and domain expiry, SSH reachability, NTP drift, and SMTP/IMAP/POP3 mail servers — and use inbound heartbeat checks as a dead-man's switch for cron jobs and workers.
A day in the life
You're shipping a new microservice and you don't want to click through a dashboard to monitor it. In your deploy pipeline you POST to the PingInsight REST API with a scoped key, creating an HTTP/API check that asserts a 200 status, a JSON field, and a sub-300ms response time. The check runs from three regions; when a canary release starts returning the right status but the wrong JSON shape, the body assertion fails and quorum confirms it within a second, paging you in Slack. You subscribe to the SSE stream to surface live status on your internal dashboard, and tear the monitor down from the same API when the service is retired — monitoring as code, no console required.
- ✓HTTP/API checks with assertions on status, body/JSON, headers, and latency
- ✓TCP, UDP, DNS, SSL, domain-expiry, SSH, and NTP checks
- ✓Mail-server checks (SMTP, IMAP, POP3) and inbound heartbeat/cron monitoring
- ✓Public REST API with scoped keys for monitoring-as-code
- ✓Server-sent events (SSE) stream for real-time status in your own dashboards
- ✓Multi-location quorum across 3 regions so flaky deploys don't false-alarm
curl -X POST https://api.pinginsight.com/v1/monitors \
-H "Authorization: Bearer $PINGINSIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "http",
"name": "Orders API",
"url": "https://api.example.com/v1/orders",
"interval_seconds": 30,
"assertions": [
{ "source": "status_code", "comparison": "equals", "target": "200" },
{ "source": "json", "property": "$.status", "comparison": "equals", "target": "ok" },
{ "source": "response_time", "comparison": "less_than", "target": "300" }
]
}'Dig into Uptime monitoring and Incident management, review pricing, or see how PingInsight compares to UptimeRobot.
Frequently asked questions
- Can I create and manage monitors entirely through the API?
- Yes. PingInsight exposes a documented REST API — the same one the dashboard uses — with scoped API keys, so you can create, update, and delete monitors, status pages, and alert channels from your deploy pipeline. There's also on-demand revalidation and an SSE stream for real-time status.
- What can HTTP/API assertions check beyond the status code?
- Assertions can validate the status code, the response body or specific JSON properties, response headers, and the response time. That means a 200 that returns the wrong payload, a missing header, or a slow response all fail the check rather than passing silently.
- Which protocols can I monitor besides HTTP?
- Fourteen check types in total: HTTP/API, ping, TCP, UDP, DNS, SSL, domain/WHOIS, heartbeat, group, mail (SMTP/IMAP/POP3), NTP, and SSH — so you can cover web services, infrastructure, mail, and scheduled jobs from one place.
- How do you keep flaky deploys from triggering false alerts?
- Checks run from three regions (us-east-2, us-west-2, eu-west-1) and an outage is only confirmed by quorum — at least two regions agreeing — combined with a consecutive-failure threshold, so a single transient blip during a rollout doesn't page you.
PingInsight for developers & API teams
Free forever. Wire up your first check with the API.