title: Create Customer IP (Customer) description: POST /api/customers/:customerPublicId/ipsCopy Anchor Link

Create Customer IP (Customer)Copy Anchor Link

POST /api/customers/:customerPublicId/ips

Creates a new customer IP for DNSBL monitoring.

Request BodyCopy Anchor Link

{
  "ipAddress": "203.0.113.10",
  "label": "Mail Server",
  "ipFamily": "v4",
  "status": "active"
}

Notes:

• customerPublicId should be the customer public UUID. Legacy numeric customer IDs remain supported for compatibility.
• ipFamily is optional; if omitted, it is inferred from the IP address.
• If ipFamily is provided, it must match the IP address version.
• Creating an active IP may be blocked by quota limits.

Example (cURL)Copy Anchor Link

BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"

curl -X POST "$BASE_URL/api/customers/6bfec6f6-245a-47ce-843b-157d97d56f88/ips" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"ipAddress":"203.0.113.10","label":"Mail Server","status":"active"}'

ResponseCopy Anchor Link

200 with the customer IP record, and the record now carries a deduplicated flag.

Repeating a request with exactly the same body does NOT create a second, separately billable monitor: the entry that already exists is returned again and the response carries "deduplicated": true, while a first creation carries "deduplicated": false. Both cases answer 200. The comparison covers the whole request and not just ipAddress, so the same address sent again with a different label or status is a different request and does create a second entry -- there is no uniqueness check on the address itself. A recognised repeat is not counted against the active-IP limit.

Common errorsCopy Anchor Link

• 400 Invalid Customer identifier when :customerPublicId is missing/invalid
• 400 Invalid IP address when ipAddress is invalid
• 400 IP family mismatch... when ipFamily does not match the IP
• 401 Unauthorized when you are not logged in
• 403 Forbidden for readonly/global supporter users, or when you cannot access the customer
• 403 Active IP limit reached... when creating/activating would exceed your quota
• 404 Customer not found when the customer does not exist
• there is no 409 on this route: an address that is already present under this customer with exactly the same body comes back as a recognised repeat (see Response), and with a different body it becomes a second entry