API problem detail
Unique Constraint Violation
Description
This problem happens when a create or update collides with an existing record on a value the database requires to be unique. The detail names the conflicting model. Nothing was written.
The most common duplicates are reported differently, as a Preflight
400 with a validation failure on the field: a clientReference already used by
your company ("Client reference [...] already exists."), and an email address already in use.
Response title: The request conflicts with an existing record..
Experience API error bodies also carry errorCode, resolution, and
traceId. Branch on errorCode, not on title or
detail; see fields on every error.
How to resolve
X-Idempotency-Key. Retrying the identical request unchanged returns the same 400.