Recipe: Status Page Monitor

Monitor AWS or any status page for service incidents.

POST /v1/monitors

curl -X POST https://api.verid.dev/v1/monitors \
  -H "Authorization: Bearer $VERID_API_KEY" \
  -d '{
    "name": "AWS Status Monitor",
    "url": "https://health.aws.amazon.com/health/status",
    "schedule_interval_seconds": 300,
    "extract_config": {
      "method": "css",
      "fields": {
        "incidents": ".current-incidents li, [data-test=incident-title]",
        "overall_status": ".overall-status"
      }
    },
    "diff_predicate": {
      "type": "any_field_changes"
    },
    "deliveries": [
      { "type": "slack", "webhookUrl": "https://hooks.slack.com/services/..." },
      { "type": "email", "to":         "oncall@yourcompany.com" }
    ]
  }'

Tip

Every plan can check as often as every minute, so you can catch incidents within minutes. Each check uses one run: a 5-minute interval is about 8,600 runs a month, which fits the Pro and Scale plans; a daily check is about 30 runs a month and fits any plan, including the 14-day free trial's 200 runs.

Or: use the template

POST /v1/monitors/from-template/aws-status-page

curl -X POST https://api.verid.dev/v1/monitors/from-template/aws-status-page \
  -H "Authorization: Bearer $VERID_API_KEY" \
  -d '{
    "name": "AWS Status",
    "deliveries": [
      { "type": "slack", "webhookUrl": "https://hooks.slack.com/services/..." }
    ]
  }'

For routing incidents to the right channel and tuning noise, see the Status Page Incident Detection use case.