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.
Another account of the brand signs in with the wallet being added (the account API): conflict says whether it is that account's only way in, and carries a move_ticket where the brand lets a way in move between accounts and that account keeps another.
What to do
Sign in with the wallet to use that account, or move the wallet here with the conflict's move_ticket where one is given.
| Field | Value |
|---|---|
code | wallet_in_use |
status | 409 Conflict |
title | Wallet in use |
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_in_use. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/wallet_in_use",
"title": "Wallet in use",
"status": 409,
"code": "wallet_in_use"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code identity_limit_reached (HTTP 409)
What Synq's `identity_limit_reached` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.
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.