LINK_TOKEN_LOOKUP_FAILED
503upstreamThe link token could not be read.
Cause
A storage fault stopped us LOOKING for the token — it is not evidence the token is absent. Retryable by design so a transient fault never reports an in-flight connect session as permanently gone.
How to fix it
Retry the status poll with backoff. Do not tear down the connect session.
Example response
503 LINK_TOKEN_LOOKUP_FAILED
JSON
{
"error_code": "LINK_TOKEN_LOOKUP_FAILED",
"error_type": "upstream",
"error_message": "The link token could not be read.",
"hint": "Retry the status poll with backoff. Do not tear down the connect session.",
"docs_url": "https://docs.billerapi.com/errors/LINK_TOKEN_LOOKUP_FAILED",
"request_id": "d94f5e2a-8c3b-4f1e-9a7d-6b2c1e0f8a34"
}Related
- Error handling — the error envelope shape and how to parse it
- Error code reference — every stable error code
Canonical docs URL: https://docs.billerapi.com/errors/LINK_TOKEN_LOOKUP_FAILED
Was this page helpful?