Error code org_domain_exists (HTTP 409)
What Synq's `org_domain_exists` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.
The org has this domain already: read it, or verify it.
What to do
Use the existing domain's id from the org's domain list instead of adding it again.
| Field | Value |
|---|---|
code | org_domain_exists |
status | 409 Conflict |
title | Domain exists |
Synq's APIs answer errors with a problem document (RFC 9457, application/problem+json). Its type is the address of this page, and its code is org_domain_exists. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/org_domain_exists",
"title": "Domain exists",
"status": 409,
"code": "org_domain_exists"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code org_domain_invalid (HTTP 422)
What Synq's `org_domain_invalid` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
Error code org_domain_limit_reached (HTTP 409)
What Synq's `org_domain_limit_reached` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.