SynqDocs
Account APIWallet moves

Move a wallet here from another account

Moves the wallet a `wallet_in_use` problem of `POST /v1/wallets` named to the signed-in person, with its `move_ticket`, within 15 minutes; the signature it was added with proved the wallet, so none is asked again, and no code. Only where the account that has it keeps another way in, and the brand moves a way in on its own proof (`move_proved_identities`, on by default) or lets ways in move between accounts (`link_conflicts: move`): the wallet alone moves, that account keeps everything else, its sessions signed in with a wallet end, its owner is emailed (“A wallet was moved off your account”), both accounts’ Discord roles and Telegram groups are checked again at once, and both record the move (`user.identity_unlinked` and `user.identity_linked`, `by: moved`, `on_own_proof: true`). Where that changed meanwhile, 409 `wallet_in_use` again, with no ticket; where the wallet left that account, 409 `conflict`: add it again. A ticket that expired, was used or isn’t the person’s answers 404. Needs `me:write`. An account that signs in with an email address nobody proved yet takes no new way to sign in: 403 `email_unverified` until the person verifies it.

POST/v1/wallet-moves

Moves the wallet a wallet_in_use problem of POST /v1/wallets named to the signed-in person, with its move_ticket, within 15 minutes; the signature it was added with proved the wallet, so none is asked again, and no code. Only where the account that has it keeps another way in, and the brand moves a way in on its own proof (move_proved_identities, on by default) or lets ways in move between accounts (link_conflicts: move): the wallet alone moves, that account keeps everything else, its sessions signed in with a wallet end, its owner is emailed (“A wallet was moved off your account”), both accounts’ Discord roles and Telegram groups are checked again at once, and both record the move (user.identity_unlinked and user.identity_linked, by: moved, on_own_proof: true). Where that changed meanwhile, 409 wallet_in_use again, with no ticket; where the wallet left that account, 409 conflict: add it again. A ticket that expired, was used or isn’t the person’s answers 404. Needs me:write. An account that signs in with an email address nobody proved yet takes no new way to sign in: 403 email_unverified until the person verifies it.

Authorization

bearer
AuthorizationBearer <token>

An access token from this issuer for its account API (resource=<issuer>/me).

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

curl -X POST "https://example.auth.synq.build/me/v1/wallet-moves" \  -H "Authorization: Bearer $ACCESS_TOKEN" \  -H "Content-Type: application/json" \  -d '{    "ticket": "string"  }'
{  "id": "idn_01h455vb4pex5vsknk084sn02q",  "address": "seedYs9i7pN9W4yJ5wUZn3tqxV4o5fH8sZ7mJm6dRKA",  "chain": "solana",  "label": "string",  "primary": true,  "created_at": "2026-10-21T12:00:00.000Z",  "last_used_at": "2026-10-21T12:00:00.000Z",  "wallet_app": "Phantom"}