Uptimeify Docs
MonitorsDomain expiry monitoring

Create Customer Domain (Customer)

title: Create Customer Domain (Customer) description: POST /api/customers/:customerPublicId/domains

Create Customer Domain (Customer)

POST /api/customers/:customerPublicId/domains

Creates a customer domain for expiry monitoring.

Request Body

{
  "domainName": "deinkunde.com",
  "label": "Main Domain",
  "status": "active",
  "expiryWarningDays": 30,
  "expiryErrorDays": 7
}

Notes:

  • customerPublicId should be the customer public UUID. Legacy numeric customer IDs remain supported for compatibility.
  • domainName must be a valid domain like deinkunde.com (no protocol, no path).
  • Creating an active domain may be blocked by quota limits.

Example (cURL)

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

curl -X POST "$BASE_URL/api/customers/6bfec6f6-245a-47ce-843b-157d97d56f88/domains" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domainName":"deinkunde.com","label":"Main Domain","status":"active","expiryWarningDays":30,"expiryErrorDays":7}'

Response

200 with the customer domain 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 domainName, so the same domain sent again with a different label, status, expiryWarningDays or expiryErrorDays is a different request and does create a second entry -- there is no uniqueness check on the domain name itself. A recognised repeat consumes no quota and never moves the organization up a quota tier.

Common errors

  • 400 Invalid Customer identifier when :customerPublicId is missing/invalid
  • 400 Invalid domain name... when domainName is invalid
  • 401 Unauthorized when you are not logged in
  • 403 Forbidden for readonly/global supporter users, or when you cannot access the customer
  • 403 Active domain limit reached... when creating/activating would exceed your quota
  • 404 Customer not found when the customer does not exist

On this page