Deep API Health Checks
API Uptime Monitoring for Developers
HTTP 200 is not a health check. upti.my validates your APIs actually work. We check response bodies, latency, and authenticated endpoints — with full timing breakdowns on every request.
Why API Monitoring Requires More Than Ping
Your API can return 200 OK while being completely broken. A database connection fails, and the endpoint returns an empty array. Auth is misconfigured, and everyone gets "null" for their profile. The service is up, but the API is useless.
Response Validation
Check that API responses contain expected data, not just status codes.
User Journey Coverage
Test complete flows like login → fetch data → verify with Playwright browser checks.
Auth Testing
Verify protected endpoints reject unauthenticated requests.
Protocol Support
HTTP, GraphQL, gRPC, TCP, DNS, SSL. All with native support.
Common API Monitoring Mistakes
Most teams set up basic monitoring and call it done. Then they find out about outages from their users instead of their tools.
- ✗Only checking /health while the main endpoints are broken due to a database issue
- ✗Ignoring response bodies because an empty array is still a 200 OK
- ✗Skipping auth endpoints so login fails, but the API "works"
- ✗No latency thresholds so 5-second response times aren't caught until users complain
How upti.my Monitors APIs Properly
upti.my treats API monitoring as first-class. Every check validates what matters: response content, timing, and protocol-specific behaviors — with a full performance breakdown for every request.
JSON Assertions
Validate fields in JSON responses with exact-match assertions.
Performance Breakdown
DNS, TCP connect, TLS handshake, TTFB, and transfer timing on every check.
Latency Thresholds
Alert when response times exceed acceptable limits.
Browser Checks
Cover multi-step journeys with scripted Playwright checks in real Chromium.
Getting Started
Set up API monitoring in the dashboard:
- 1
Create a Monitor
Click "New Monitor" and select your protocol: HTTP, GraphQL, gRPC, TCP, DNS, or SSL.
- 2
Enter Your Endpoint
Add your URL, authentication headers, and any request body needed.
- 3
Add Assertions
Define what success looks like: status codes, response body fields, latency limits.
- 4
Set Alert Channels
Connect Slack, Discord, PagerDuty, or webhooks. Get notified your way.
Frequently Asked Questions
API monitoring goes beyond checking if a URL returns 200 OK. It validates response bodies, authentication, and response times, and captures a full performance breakdown (DNS, TCP connect, TLS handshake, TTFB, content transfer) on every check. For complete user flows, Playwright browser checks script real journeys in Chromium.
Yes. upti.my supports header-based authentication: Bearer tokens, API keys, and Basic auth, all sent via custom headers you configure. Credentials are encrypted and never logged.
upti.my has native support for GraphQL queries/mutations and gRPC services. You define the query or method to call, and we validate the response matches your expectations.
Yes — with Playwright browser checks. They run real Chromium and script complete journeys like log in, load data, verify the result, with assertions at every step. HTTP checks handle individual endpoints; Playwright covers the flows between them.
Failed checks trigger immediate alerts via your configured channels. The incident includes the full request/response details, timing, and which assertion failed.
Related Topics
HTTP Monitoring
Deep HTTP/HTTPS health checks with full request/response validation.
gRPC Monitoring
Monitor gRPC services and unary/streaming RPCs.
GraphQL Monitoring
Execute GraphQL queries and validate response data.
TCP Monitoring
Monitor any TCP port or service.
DNS Monitoring
Track DNS resolution and propagation.
SSL/TLS Monitoring
Certificate expiry and chain validation.
Cron Job Monitoring
Heartbeat monitoring for scheduled tasks.
Run reliability as one connected workflow
Detect failures early, route alerts clearly, coordinate incidents, and keep status updates in sync from one system.