HTTP / HTTPS Health Checks

Overview

HTTP health checks are the most versatile monitoring type in upti.my. They allow you to send fully customizable HTTP requests to any endpoint and validate the response against your expected criteria. Whether you're monitoring a simple website, a REST API, or a complex web service, HTTP checks give you complete control over request configuration and response validation.

Supported HTTP Methods

upti.my supports all standard HTTP methods, enabling you to monitor any type of API endpoint:

• GET - Retrieve resources and verify response content
• POST - Test API endpoints that accept data submissions
• PUT - Validate update endpoints with request bodies
• DELETE - Monitor deletion endpoints for availability
• PATCH - Check partial update endpoints
• HEAD - Lightweight checks that only retrieve headers
• OPTIONS - Verify CORS configuration and allowed methods

Request Configuration

Custom Request Headers

Add any number of custom headers to your request. This is essential for APIs that require authentication tokens, content-type specifications, or custom identifiers.

{
  "Authorization": "Bearer your-api-token",
  "Content-Type": "application/json",
  "X-Custom-Header": "monitoring-check"
}

Request Body

For POST, PUT, and PATCH requests, you can include a JSON request body. This allows you to test endpoints that expect specific payloads.

{
  "action": "health_check",
  "timestamp": "2025-01-01T00:00:00Z"
}

Expected Status Code

Define the HTTP status code you expect from a healthy response. By default, upti.my expects a 200 OK response. You can change this to any valid status code, such as201, 204, or 301, depending on your endpoint's behavior.

Expected Response Body

Go beyond status code validation by checking the actual response body. You can specify a string that must appear in the response for the check to be considered successful. This is useful for verifying that your API returns the correct data, not just a successful status code.

Proxy Support

Route your HTTP checks through a proxy server for scenarios that require it. upti.my supports three proxy types:

• HTTP Proxy - Standard HTTP proxy for unencrypted traffic
• HTTPS Proxy - Encrypted proxy connection for secure requests
• SOCKS5 Proxy - Versatile proxy protocol supporting any TCP traffic

Response Data

Every HTTP check execution captures detailed response data for analysis and debugging:

Performance Breakdown

upti.my provides a detailed request performance breakdown so you can identify exactly where latency occurs in the request lifecycle:

Example Configuration

{
  "method": "GET",
  "url": "https://api.example.com/health",
  "headers": {
    "Authorization": "Bearer token123"
  },
  "expected_status_code": 200,
  "expected_response_body": ""status":"ok"",
  "timeout_seconds": 10,
  "interval_seconds": 30
}