Error code scope_not_allowed (HTTP 422)
What Synq's `scope_not_allowed` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
A scope a brand or org asked a sign-in provider for that isn't on Synq's reviewed list for it: GET /v1/provider-scopes lists those it allows. Each one refused is in errors, by its pointer.
What to do
Ask only for scopes listed at GET /v1/provider-scopes for that provider.
| Field | Value |
|---|---|
code | scope_not_allowed |
status | 422 Unprocessable Content |
title | Scope not allowed |
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 scope_not_allowed. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/scope_not_allowed",
"title": "Scope not allowed",
"status": 422,
"code": "scope_not_allowed"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code provider_unreachable (HTTP 502)
What Synq's `provider_unreachable` error code means, when the API answers HTTP 502 Bad Gateway with it, and how to fix it.
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.