User onboarding & device registration
Login now triggers verification emails, and users are activated through a device-registration flow:- The first user to log into the mobile app is approved automatically and becomes active right away.
- For every subsequent user, after they setup and login, we create a device-registration request. An admin simply approves that request for the user to become active.
What changed at a glance
1) Vaults
- templateId is no longer required — remove it from your createVault payload.
- To add a vault to vault groups, pass the new vaultGroupIds param (array of group IDs from the UI).
- Vault creation now needs approval — do it as 2 separate calls, then poll for wallets: // 2. Approve the change request await apiClient.createVaultApproval(vault);
2) Contacts
- To add a contact to contact groups, pass the contactGroupIds param on create.
- Contact creation needs approval — 2 separate calls:
- To update the contact groups on an already-created contact:
3) Transactions
- Create a transfer:
- After creation the transaction is PENDING; approve it: