Error code provider_url_unsafe (HTTP 422)
What Synq's `provider_url_unsafe` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
A brand's own sign-in provider names an address Synq never reaches: not https, or off the public internet (a private, loopback or link-local address, a local name, or a name that resolves to one), as the URL itself, its discovery document or its token endpoint says. errors names each field, where the request sent it.
What to do
Use the provider's public https addresses, reachable from the internet.
| Field | Value |
|---|---|
code | provider_url_unsafe |
status | 422 Unprocessable Content |
title | Provider URL unsafe |
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 provider_url_unsafe. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/provider_url_unsafe",
"title": "Provider URL unsafe",
"status": 422,
"code": "provider_url_unsafe"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code scope_needs_own_app (HTTP 422)
What Synq's `scope_needs_own_app` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
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.