Error code no_way_to_sign_in (HTTP 422)
What Synq's `no_way_to_sign_in` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
The change would leave the brand with no way to sign in on its page: every way off, or off only for new people. At least one way stays shown or more; a provider set to link only doesn't count.
What to do
Keep at least one way to sign in shown or under More ways, then turn the others off.
| Field | Value |
|---|---|
code | no_way_to_sign_in |
status | 422 Unprocessable Content |
title | No way to sign in |
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 no_way_to_sign_in. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/no_way_to_sign_in",
"title": "No way to sign in",
"status": 422,
"code": "no_way_to_sign_in"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code too_many_shown (HTTP 422)
What Synq's `too_many_shown` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
Error code scope_unavailable (HTTP 422)
What Synq's `scope_unavailable` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.