Error code sign_in_provider_exists (HTTP 409)
What Synq's `sign_in_provider_exists` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.
The brand has a sign-in provider of its own with this id already: ids are unique in a brand.
What to do
Pick another id, or change the provider that has it.
| Field | Value |
|---|---|
code | sign_in_provider_exists |
status | 409 Conflict |
title | Sign-in provider 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 sign_in_provider_exists. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/sign_in_provider_exists",
"title": "Sign-in provider exists",
"status": 409,
"code": "sign_in_provider_exists"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code provider_discovery_failed (HTTP 422)
What Synq's `provider_discovery_failed` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
Error code sign_in_method_in_use (HTTP 409)
What Synq's `sign_in_method_in_use` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.