Error code wallet_signature_rejected (HTTP 400)
What Synq's `wallet_signature_rejected` error code means, when the API answers HTTP 400 Bad Request with it, and how to fix it.
A wallet's signature didn't check out (the account API): its sign-in request expired or was used, the calling app didn't ask for it, or the signature isn't the wallet's over it. reason says which.
What to do
Ask the issuer for a new sign-in request from the app's own page, have the wallet sign it, and send it within 5 minutes.
| Field | Value |
|---|---|
code | wallet_signature_rejected |
status | 400 Bad Request |
title | Wallet signature rejected |
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 wallet_signature_rejected. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/wallet_signature_rejected",
"title": "Wallet signature rejected",
"status": 400,
"code": "wallet_signature_rejected"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code wallet_in_use (HTTP 409)
What Synq's `wallet_in_use` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.
Error code link_result_invalid (HTTP 400)
What Synq's `link_result_invalid` error code means, when the API answers HTTP 400 Bad Request with it, and how to fix it.