Create a Monitor
Set up an uptime monitor to track the health of your APIs and websites.
From the dashboard
- Navigate to the Monitors section
- Click New Monitor
- Configure the monitor:
- Name — a descriptive label (e.g., "Production API")
- URL — the endpoint to monitor (e.g.,
https://api.example.com/health) - Method — HTTP method to use (default: GET)
- Interval — check frequency (e.g., every 5 minutes)
- Expected status — HTTP status code that indicates healthy (default: 200)
- Timeout — seconds to wait before marking as down
- Click Create
From the API
curl -X POST https://app.hooklistener.com/api/v1/uptime-monitors \
-H "Authorization: Bearer hklst_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"uptime_monitor": {
"name": "Production API",
"url": "https://api.example.com/health",
"method": "GET",
"interval_seconds": 300,
"expected_status_code": 200,
"timeout_ms": 30000
}
}'
From the MCP server
Ask your AI assistant:
"Create an uptime monitor for https://api.example.com/health that checks every 5 minutes"
Configuration options
| Field | Type | Default | Description |
|---|---|---|---|
name | string | required | Monitor display name (max 255 chars) |
url | string | required | URL to monitor |
method | string | GET | HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD) |
check_interval | integer | 5 | Check interval in minutes (1, 5, 10, 30, or 60) |
expected_status_code | integer | 200 | Expected healthy status code (100-599) |
body_contains | string | null | String that must appear in the response body |
failure_threshold | integer | 2 | Consecutive failures before marking as down (1-10) |
headers | object | {} | Custom request headers |
timeout_ms | integer | 30000 | Request timeout in milliseconds |
body | string | null | Request body (for POST/PUT) |
email_enabled | boolean | true | Send email alerts on status change |
slack_enabled | boolean | false | Send Slack alerts on status change |
Monitoring intervals
Available check intervals: 1, 5, 10, 30, or 60 minutes. Minimum interval depends on your plan:
| Plan | Minimum interval |
|---|---|
| Free | 15 minutes |
| Pro | 1 minute |
| Business | 1 minute |
Failure threshold
To avoid false positives from transient network issues, monitors require multiple consecutive failures before marking a service as down. The default threshold is 2, meaning the monitor must fail 2 checks in a row before alerting. You can configure this from 1 (alert immediately) to 10.
After creation
Once created, the monitor starts checking immediately. You can:
- View check history and response times in the dashboard
- Configure alerts for status changes
- Add it to a status page
- Edit or pause the monitor at any time