Blog · Engineering

UptimeRobot Webhooks to WakeUp Dev: Zero‑Downtime Alerting

UptimeRobot Webhooks to WakeUp Dev: Zero‑Downtime Alerting

Learn how to wire UptimeRobot webhooks to WakeUp Dev’s POST /v1/alert, leveraging unlimited seats and pay‑per‑voice to keep on‑call teams focused.

· Enrique Drack

WakeUp Dev’s voice‑first on‑call platform is built to ingest alerts from any webhook source, including UptimeRobot. By sending a single JSON payload to POST https://api.wakeupdev.com/v1/alert with your x‑api‑key, you can trigger a digit‑1 ACK call that routes the alert to the appropriate on‑call engineer without the overhead of per‑seat licensing.

Configuring UptimeRobot Webhooks

UptimeRobot supports a simple HTTP POST webhook that fires whenever a monitored URL goes down or comes back up. In the UptimeRobot dashboard:

  • Create a new monitor or edit an existing one.
  • Under “Alert Contacts” add a new contact type “Webhook”.
  • Paste the WakeUp Dev webhook URL: https://api.wakeupdev.com/v1/alert.
  • Enable the “Send JSON” option so the payload contains status, hostname, and other metadata.

The webhook payload looks like this:

{
  "hostname":"app.example.com",
  "status":"down",
  "time":"2026-09-29T12:34:56Z",
  "message":"HTTP 500"
}

Sending Alerts to WakeUp Dev

WakeUp Dev expects a minimal JSON body with the fields title, description, and an optional metadata map. The following cURL example shows how to forward the UptimeRobot payload:

curl -X POST https://api.wakeupdev.com/v1/alert \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "title": "UptimeRobot: app.example.com is down",
    "description": "HTTP 500 from UptimeRobot monitor",
    "metadata": {
      "hostname": "app.example.com",
      "status": "down",
      "time": "2026-09-29T12:34:56Z"
    }
  }'

WakeUp Dev will immediately place a voice call to the on‑call engineer. The engineer presses 1 to ACK, and the call ends, eliminating the need for a live operator or a separate ticketing system.

Cost Advantages

Because WakeUp Dev charges per voice alert rather than per seat, you can add as many engineers as you need without incurring extra licensing fees. The pay‑per‑alert model scales with actual incidents, not with the number of team members. In a typical 30‑engineer squad, the cost savings compared to a per‑seat SaaS can reach 70% or more.

By combining UptimeRobot’s free monitoring tier with WakeUp Dev’s unlimited‑seat, pay‑per‑voice architecture, you get a low‑cost, high‑reliability alerting pipeline that keeps on‑call fatigue to a minimum.

💬 SRE & DevOps Insights

What strategies do you use to keep alerting costs under control while maintaining rapid incident response?

Write to administrador@wakeupdev.com or continue from the FAQ.

UptimeRobot Webhooks to WakeUp Dev: Zero‑Downtime Alerting | WakeUp Dev