Add a wallet with its signature
Adds the wallet that signed a sign-in request this app’s page asked the issuer for (`POST /siws/nonce` with the app’s client id, from a page on one of its redirect origins): one signature, from the app’s own page, with no hosted page. The request works for 5 minutes, once, and only for the app that asked for it (`wallet_signature_rejected`, with `reason`: `malformed`, `unknown_request`, `request_expired`, `request_used` or `bad_signature`). Their first wallet becomes their primary one. A wallet that is theirs already answers 200 and is left as it is. A wallet another account of the brand signs in with joins this one only where that account is empty and the brand merges empty accounts (`merge_empty_accounts`: the wallet is its only way in, and it holds nothing else): that account is merged in and deleted at once, the answer's `merged_from` is its `sub`, and `user.merged` then `user.deleted` are recorded for it. Otherwise it is never merged: 409 `wallet_in_use`, whose `conflict` says whether it is that account’s only way in and, where that account keeps another 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`), carries a `move_ticket` for `POST /v1/wallet-moves`: the signature just made is all the proof it needs. A brand or app that doesn’t take wallets answers 409 `sign_in_method_unavailable`; one person has at most 20 ways to sign in (409 `identity_limit_reached`). Needs `me:write`, from a sign-in on this device within the brand's `link_reauth_window` (2 hours unless the tenant chose otherwise), whichever way it was made, or from the last 5 minutes whose time Synq proved, else 403 `fresh_sign_in_required`, whose `confirm_with` names the way it was made: show the person what happens and why, then send them to sign in with `max_age=0` and `synq_method` set to it. 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. Recorded as `user.identity_linked`, with `confirmed_by: recent_sign_in` and the `new_device` and `new_ip` signals.
/v1/walletsAdds the wallet that signed a sign-in request this app’s page asked the issuer for (POST /siws/nonce with the app’s client id, from a page on one of its redirect origins): one signature, from the app’s own page, with no hosted page. The request works for 5 minutes, once, and only for the app that asked for it (wallet_signature_rejected, with reason: malformed, unknown_request, request_expired, request_used or bad_signature). Their first wallet becomes their primary one. A wallet that is theirs already answers 200 and is left as it is. A wallet another account of the brand signs in with joins this one only where that account is empty and the brand merges empty accounts (merge_empty_accounts: the wallet is its only way in, and it holds nothing else): that account is merged in and deleted at once, the answer's merged_from is its sub, and user.merged then user.deleted are recorded for it. Otherwise it is never merged: 409 wallet_in_use, whose conflict says whether it is that account’s only way in and, where that account keeps another 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), carries a move_ticket for POST /v1/wallet-moves: the signature just made is all the proof it needs. A brand or app that doesn’t take wallets answers 409 sign_in_method_unavailable; one person has at most 20 ways to sign in (409 identity_limit_reached). Needs me:write, from a sign-in on this device within the brand's link_reauth_window (2 hours unless the tenant chose otherwise), whichever way it was made, or from the last 5 minutes whose time Synq proved, else 403 fresh_sign_in_required, whose confirm_with names the way it was made: show the person what happens and why, then send them to sign in with max_age=0 and synq_method set to it. 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. Recorded as user.identity_linked, with confirmed_by: recent_sign_in and the new_device and new_ip signals.
Authorization
bearer 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/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/wallets" \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "siws": "eyJhZGRyZXNzIjoic2VlZFlzOWk3cE45VzR5SjV3VVpuM3RxeFY0bzVmSDhzWjdtSm02ZFJLQSJ9" }'{ "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", "merged_from": "usr_01h455vb4pex5vsknk084sn02q"}