Bulk creation of new vault accounts
Create multiple vault accounts by running an async job.
- The HBAR, TON, SUI, TERRA, ALGO, and DOT blockchains are not supported.
- These endpoints are currently in beta and might be subject to changes.
- Limited to a maximum of 10,000 accounts per operation.
- With
vaultType: KEY_LINK, creates Key Link vault accounts; setautoAssign: trueto bind them to the workspace’s signing keys (seevaultTypeandautoAssign).
Endpoint Permissions: Admin, Non-Signing Admin, Signer, Approver, Editor.
Headers
Body
Type of vault accounts to create. The default type is MPC. KEY_LINK creates Key Link vault accounts. It requires a Key Link workspace. With autoAssign set to true, the vault accounts are bound to the workspace's Key Link signing keys, assigned automatically from the available keys, and only one KEY_LINK bulk creation with autoAssign set to true can run per workspace at a time. With autoAssign set to false (the default), the vault accounts are created without keys. With KEY_LINK, names, vaultAccountNamesStartingIndex, prefix and tagIds work as they do for MPC, and baseAssetIds may be empty to create vault accounts without wallets.
MPC, KEY_LINK "KEY_LINK"
Applicable only when vaultType is KEY_LINK. For MPC, this parameter is ignored. If set to true, keys are assigned to every created vault account. If there are not enough available keys to assign, the request returns an error and no vault accounts are created. If set to false, the vault accounts are created without any keys, and baseAssetIds must be empty because wallets can only be created for vault accounts that have keys.
true