Verify Domain
Verifies DNS TXT records for a custom domain. Admin-only.
POST /api/organization/whitelabel/domains/verify
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
domainId | number | Yes | The domain ID to verify |
Example (cURL)
curl -X POST "$BASE_URL/api/organization/whitelabel/domains/verify" \
-H "Cookie: $SESSION_COOKIE" \
-H "Content-Type: application/json" \
-d '{ "domainId": 2 }'Response (success)
{
"verified": true,
"status": "verified",
"domain": {
"id": 2,
"hostname": "app.deinkunde.com",
"status": "verified",
"role": "app",
"isPrimary": false,
"verificationToken": "xyz789-abc456",
"verifiedAt": "2026-04-15T12:30:00.000Z",
"lastVerificationError": null,
"lastVerificationErrorAt": null,
"createdAt": "2026-04-15T12:00:00.000Z",
"updatedAt": "2026-04-15T12:30:00.000Z"
}
}Common errors
400 domainVerificationFailedwhen the TXT record was not found. The error data says what we saw, so you can fix the record without guessing:
{
"statusCode": 400,
"statusMessage": "TXT verification failed (token not found)",
"data": {
"code": "domainVerificationFailed",
"recordName": "_verify-status.app.example.com",
"expected": "xyz789-abc456",
"lookup": "records",
"observed": ["old-token-from-another-tool"],
"nameservers": { "zone": "example.com", "hosts": ["ns1.dns-provider.example", "ns2.dns-provider.example"] },
"authoritative": { "nameserver": "ns1.dns-provider.example", "lookup": "records", "observed": ["a1b2c3d4e5f6"] },
"propagation": "propagating"
}
}lookup is records (TXT values found, none matches; they are in observed, at most 10), noRecords (the name exists but has no TXT record), nxdomain (the name does not exist), timeout or error (resolver failure, retry later).
nameservers is the zone the hostname is delegated in and its authoritative nameservers (null if that could not be determined). authoritative is what one of those nameservers answered when asked directly for recordName, bypassing every cache (null if none could be asked; only public addresses are queried). propagation reads both answers: propagating (your nameserver has the token, our resolver does not see it yet, retry after the TTL), not_published (not even your nameserver has it), unknown (no nameserver could be asked).
The failure is also stored on the domain: every domain response carries it as lastVerificationError with lastVerificationErrorAt until the next successful verification clears both.
400 Domain has no verification token404 Domain not found409 Conflict(domainAlreadyClaimed) when another organization has already verified or activated this hostname. The owner is not disclosed.
Upload Branding Asset
Uploads a logo or favicon as a base64 data URL. Assets are stored in S3 and the branding record is updated automatically. Requires admin role.
Notification Channels
Manage how and where alerts are delivered. Channels can be organization-level (default for all customers), customer-level (override for a specific customer), or website-level (override for a specific monitor).