Skip to main content
Your organization has been onboarded to the more flexible Policy Rule-Based Framework. This guide covers what changed on the platform and the API updates you need to integrate. Help center article: https://docs.primevault.com/help-center/policy-engine

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.
This extra step ensures every new user is verified before gaining access to the platform.

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:

4) Webhook structure

Webhook events now use version: “2.0.0” with the following transaction payload:

Migration checklist