GET /v0/wallets/{id}/assets — Returns a JSON body listing the wallet’s balances with _links for navigation.
Nothing here is a toy. The call you make in five minutes is the call you run in production.
Prerequisites
- A Platform API JWT from your configured auth provider (Dynamic Labs, Privy, or ). See Authentication.
- Your platform’s base URL —
https://api.sumvin.com/v0. - A wallet address for the user () on Sei (
chain_id: 1329). - Your
x-juno-orgidif your credentials span multiple Sumvin organisations (see Authentication). Single-org integrations can omit this header.
The Platform API uses the
x-juno-jwt header (no Bearer prefix). Reserve Authorization: Bearer for SIS API calls. Multi-tenant callers also pass x-juno-orgid: <your-org-id> to scope the request to a specific organisation.Create the user
Register the user with their primary EOA address. Sumvin queues a Safe smart account for deployment on the specified chain in the background — you do not wait for it here.Response: If the user already exists, you get
201 Created208 Already Reported with the existing record.Check onboarding status
The onboarding state machine tells you which step the user is on. Response: The server drives the transitions — you submit the prompted data for each step until
is_complete: true gates the next step.200 OKis_complete is true. See the onboarding guide for the full flow, including phone and KYC.Add a wallet
Once onboarding completes, add the user’s wallet. If you use Dynamic Labs, pass the Response: For auth providers that do not issue credential IDs, use the SIWE challenge/verify flow instead — see the wallets guide for all three ownership verification methods.
credential_id from the user’s verified credential — Sumvin resolves the address and chain from Dynamic’s API.201 CreatedQuery wallet balances
This is the working artefact. The response lists token balances with USD valuations, plus HAL Response:
_links to navigate to the wallet itself and set-primary action.200 OKYou have a live Sumvin integration. The
_links field is how every response advertises its next actions — use them instead of hardcoding URLs.What’s next
| Next | Where | When |
|---|---|---|
| Full account flow | Stand up an account | Before putting real users through KYC and Safe deployment |
| Auth reference | Authentication | When you’re wiring up your JWT provider or SIS key |
| API conventions | API conventions | When a response shape surprises you — HAL, 7807, expand, 202 patterns |
| Wallet depth | Wallets guide | When you need multi-chain or manual Safe flows |