GET /v1/auth/wallets
List the wallets linked to the signed-in account — at most one per chain family (EVM, Solana).
https://triport.io/v1/auth/wallets- Network
- — (EVM and Solana wallets)
- Auth
- Console session cookie (nl_session)
Every Triport account has at most one linked wallet per chain family:
evm (Ethereum, Polygon, BSC share one address) and solana. The linked
wallet is the only wallet allowed to pay in-app invoices on that family's rails —
see Build in-app transaction. New Tron wallets can
no longer be linked or used to sign in (400 chain_not_supported); a tron row
linked before 2026-09-29 is still listed.
A wallet becomes linked in one of two ways:
source: "login"— the account was created or signed in with that wallet (wallet/verify); the sign-in wallet is the binding.source: "link"— the wallet was attached to an existing account withPOST /v1/auth/wallet/link.
There is no self-service replace or unlink: to change or remove a linked
wallet, the user contacts support and an operator changes it (audited). The
former POST /v1/auth/wallet/replace now answers 410 endpoint_removed.
Previous bindings are kept in an audited history that is not returned here.
Parameters
None.
Response
200 OK
wallets[]arraywallets[].familystringevm or solana (tron only for a binding made before 2026-09-29).wallets[].addressstring0x…, Solana base58, Tron base58 T….wallets[].linked_atstring (RFC 3339)wallets[].sourcestringlogin (sign-in wallet) or link (attached later).Errors
| Code | HTTP | When it happens |
|---|---|---|
unauthenticated | 401 | No valid session cookie. |
method_not_allowed | 405 | A method other than GET/HEAD. |
internal | 500 | Server-side failure. |
Notes
- Accounts created before 2026-09-27 may still have more than one wallet in a family; every one of them is listed and counts as linked until an operator replace collapses the family to one.
- Family names here (
solana) differ from the railfamilyvalues inGET /v1/billing/rails(sol);evmandtronmatch.