upti.my

Deep HTTP/HTTPS Health Checks

HTTP API Monitoring

A 200 OK doesn't mean your API works. upti.my validates response bodies, headers, timing, and SSL. We catch failures that basic monitoring misses.

HTTP Monitoring Done Right

HTTP endpoints fail in subtle ways. The server responds, but the response is wrong. The API is slow, but not down. The SSL certificate expires at 2 AM on Saturday. Basic ping monitoring catches none of this.

Response Validation

Check specific JSON fields, not just status codes.

Latency Monitoring

Catch slow endpoints before they affect users.

SSL Monitoring

Get alerts before certificates expire.

Multi-Region

Check from multiple locations to catch regional issues.

When HTTP 200 Is a Lie

Real examples of "working" endpoints that were broken:

  • Database connection lost so the API returns { data: [] } instead of user records
  • Cache server down causing responses to take 8 seconds instead of 200ms
  • SSL misconfigured so it works in Chrome but fails in mobile apps
  • CDN caching error page so users see stale error HTML

upti.my HTTP Checks

Every HTTP check in upti.my can validate multiple aspects of the response:

Status Code

Expect 200, 201, or any specific code.

Response Body

JSONPath assertions for specific fields.

Headers

Validate Content-Type, CORS, caching headers.

Response Time

Warning and critical latency thresholds.

Getting Started

Set up HTTP monitoring in minutes:

  1. 1

    Add Your Endpoint

    Enter your API URL and select the HTTP method (GET, POST, PUT, DELETE).

  2. 2

    Configure Authentication

    Add Bearer tokens, API keys, or custom headers. Credentials are encrypted and never logged.

  3. 3

    Define Response Assertions

    Set expected status codes, validate JSON fields with JSONPath, check headers, and set latency thresholds.

  4. 4

    Enable SSL Monitoring

    Turn on certificate expiry alerts. Get notified 14 days before your cert expires.

  5. 5

    Pick Check Regions

    Select US, EU, and Asia regions to catch location-specific issues.

Frequently Asked Questions

What HTTP methods does upti.my support?

upti.my supports all standard HTTP methods: GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS. You can send request bodies and custom headers with any method.

Can I validate JSON response bodies?

Yes. Use JSONPath expressions to validate specific fields in the response. Check for existence, equality, contains, regex matches, and numeric comparisons.

Does upti.my monitor SSL certificate expiration?

Yes. SSL certificate monitoring is built-in. You'll get alerts before your certificate expires, and we check for common SSL misconfigurations.

How do I handle authentication?

upti.my supports Bearer tokens, API keys, Basic auth, and custom headers. Credentials are stored encrypted and never logged in check results.

Can I set different thresholds for response time?

Yes. Set warning and critical thresholds for response time. A slow endpoint can trigger a warning alert before it becomes completely unresponsive.

Related Topics

Ready to start monitoring?

Set up your first health check in under 2 minutes. No credit card required.