Error code provider_token_unavailable (HTTP 409)
What Synq's `provider_token_unavailable` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.
Synq keeps no token at the provider for this identity: the brand doesn't keep them there (keep_tokens), the person's last sign-in or link went through Synq's shared app, or the access token expired and the provider gives no way to refresh it (Telegram's, an hour long).
What to do
Turn keep_tokens on with your own app at the provider, then have the person sign in or link it again; for a provider without refresh tokens, read the token within its lifetime.
| Field | Value |
|---|---|
code | provider_token_unavailable |
status | 409 Conflict |
title | Provider token unavailable |
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_token_unavailable. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/provider_token_unavailable",
"title": "Provider token unavailable",
"status": 409,
"code": "provider_token_unavailable"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code own_app_required (HTTP 422)
What Synq's `own_app_required` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
Error code provider_token_revoked (HTTP 409)
What Synq's `provider_token_revoked` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.