Uptimeify

Create a customer + all monitor types

Example automation: create one website and then create one monitor of each type.

Create a customer + all monitor types

This example is useful if you want to bootstrap a customer with a complete monitoring baseline.

High-level flow:

  1. Create customer
  2. Create website
  3. Create monitors (one per monitor type)

1) Create customer + website

Reuse:

2) Create monitors (one per type)

Monitor APIs are organized by type.

API reference overview:

Typical types you might create:

  • DNS Monitor
  • ICMP Monitor
  • SMTP Monitor
  • SSH Monitor
  • FTP Monitor
  • IMAP/POP Monitor

For details and required fields, follow the per-type API docs.

Example: create a DNS monitor

curl -X POST "$API_BASE_URL/api/dns-monitors" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "customerId": 123,
    "name": "DNS: acme.example",
    "hostname": "acme.example",
    "dnsConfig": {
      "rrtypes": ["A", "AAAA"],
      "matchMode": "exact",
      "expectedValues": {
        "A": ["93.184.216.34"],
        "AAAA": ["2606:2800:220:1:248:1893:25c8:1946"]
      }
    }
  }'

Example: create an ICMP monitor

curl -X POST "$API_BASE_URL/api/icmp-monitors" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "customerId": 123,
    "name": "Ping: gateway",
    "hostname": "gateway.acme.example"
  }'

Notes

  • Not every installation exposes every monitor type, and required fields can vary (plan/package).
  • For website (HTTP) checks, start with the website’s own monitoring settings: Website Configuration API