Domain Conflict

domain-conflict · 409

Another custom domain on the platform already has this hostname, so nothing was written.

conflictField names the field and conflictValue the value it refused.

Besides the members every error carries, this type adds resourceType, conflictField and conflictValue.

Common causes

  • Another custom domain on the platform already uses that hostname.
  • The same create was sent twice and the first one went through, so the second meets its result.
  • The hostname is on another service, maybe in another workspace: a hostname belongs to one service on the whole platform.

How to fix the call

  • Read conflictField and conflictValue: together they say which value was refused.
  • Pick another hostname, or fetch the custom domain that has it and use that one.
  • If the duplicate is your own retry, treat the call as done, not failed.
  • Send an Idempotency-Key header on writes, so a retry replays the first answer instead of colliding with it.

Example response

json
{
  "type": "domain-conflict",
  "title": "Domain Conflict",
  "detail": "A domain with hostname 'app.example.com' already exists",
  "resourceType": "Domain",
  "conflictField": "hostname",
  "conflictValue": "app.example.com",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/domains",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/domains",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/domain-conflict"
}