Skip to main content

Create a Monitor

Set up an uptime monitor to track the health of your APIs and websites.

From the dashboard​

  1. Navigate to the Monitors section
  2. Click New Monitor
  3. 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
  4. 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​

FieldTypeDefaultDescription
namestringrequiredMonitor display name (max 255 chars)
urlstringrequiredURL to monitor
methodstringGETHTTP method (GET, POST, PUT, PATCH, DELETE, HEAD)
check_intervalinteger5Check interval in minutes (1, 5, 10, 30, or 60)
expected_status_codeinteger200Expected healthy status code (100-599)
body_containsstringnullString that must appear in the response body
failure_thresholdinteger2Consecutive failures before marking as down (1-10)
headersobject{}Custom request headers
timeout_msinteger30000Request timeout in milliseconds
bodystringnullRequest body (for POST/PUT)
email_enabledbooleantrueSend email alerts on status change

Monitoring intervals​

Available check intervals: 1, 5, 10, 30, or 60 minutes, on every plan. The default is 5 minutes. The number of monitors you can create depends on your plan; see Plans & Billing.

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: