Scheduled Health Check Pings

Monitor API and service health with scheduled HTTP pings via TrigRun. Detect downtime in minutes with automatic retries and failure alerts.

Ping your APIs and services every few minutes to detect outages fast. TrigRun calls your health endpoint, checks the response, and alerts you on failure — no uptime monitoring service needed for basic checks.

The problem

You want to know within minutes if your API goes down. Dedicated monitoring tools (Cronitor, Datadog, Pingdom) are powerful but expensive for simple health checks. You just need something to hit /health every 5 minutes and tell you if it stops returning 200.

The TrigRun solution

Setting	Value
Schedule	`/5 * * *` (every 5 minutes)
Method	`GET`
Timeout	10 seconds
Retries	2 attempts (avoid false positives)
Success statuses	`200`

Create via API

curl -X POST https://api.trigrun.com/v1/jobs \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Health check - Production API",
    "kind": "cron",
    "schedule": {
      "cron": "*/5 * * * *"
    },
    "request": {
      "url": "https://api.yourapp.com/health",
      "method": "GET",
      "timeout_seconds": 10,
      "success_statuses": [200]
    },
    "retry_policy": {
      "max_attempts": 2,
      "retry_on_statuses": [500, 502, 503, 504, 429]
    }
  }'

Then attach a Slack notification rule for failures:

curl -X POST https://api.trigrun.com/v1/jobs/JOB_ID/notification-rules \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "channel_id": "YOUR_SLACK_CHANNEL_ID",
    "event": "on_failure"
  }'

Monitor multiple services

Create one job per service to track each independently:

Job name	URL	Schedule
Health check - API	`https://api.yourapp.com/health`	`/5 * * *`
Health check - Web	`https://yourapp.com/`	`/5 * * *`
Health check - Auth	`https://auth.yourapp.com/health`	`/5 * * *`
Health check - Worker	`https://worker.yourapp.com/health`	`/10 * * *`

Each job gets its own execution history, retry policy, and notification rules. View failures across all services in the TrigRun dashboard.

Common schedules

Frequency	Expression	Use case
Every minute	`* * * * *`	Critical payment APIs
Every 5 minutes	`/5 * * *`	Production services
Every 15 minutes	`/15 * * *`	Internal tools
Every hour	`0 * * * *`	Low-priority services