---
title: "Create a customer + all monitor types"
description: "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:

- [Create a customer + website](/api/examples/create-customer-and-website)

## 2) Create monitors (one per type)

Monitor APIs are organized by type.

API reference overview:

- [Monitors API](/api/monitors)

Typical types you might create:

- DNS Monitor
- ICMP Monitor
- SMTP Monitor
- SSH Monitor
- TCP Port Monitor
- FTP Monitor
- IMAP/POP Monitor

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

### Example: create a DNS monitor

```bash
curl -X POST "$API_BASE_URL/api/dns-monitors" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "customerId": 123,
    "name": "DNS: deinkunde.com",
    "hostname": "deinkunde.com",
    "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

```bash
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.deinkunde.com"
  }'
```

### Example: create a TCP Port monitor

```bash
curl -X POST "$API_BASE_URL/api/tcp-monitors" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "customerId": 123,
    "name": "Redis Primary",
    "hostname": "redis.deinkunde.com",
    "port": 6379,
    "config": { "expectBanner": "+PONG" }
  }'
```

## 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](/api/website-configuration)

