Skip to main content
MicroVaults are in private preview for enabled sandbox organizations on Ethereum Sepolia.

Prerequisites

  • A sandbox organization with MicroVaults enabled
  • A Ground sandbox API key
  • curl, jq, and uuidgen

1. Complete onboarding

Continue when onboarding is active, the managed authority is ready, and CUSTOMER_ID is non-empty. If setup is still progressing, repeat these reads after a short delay. The onboarding request is idempotent.

2. Create the vault

The response prepares and simulates a create_vault authorization. When turnkeyActivityId is present, approval has already started through the managed authority. Otherwise, sign the returned signingPayload and submit the signature to POST /v2/microvaults/authorizations/{intentId}/relay.

3. Wait for the vault to become active

Poll the authorization until it is confirmed or executed:
Then poll the vault list. The new vault first appears under provisionings and moves to items when it is active.

4. Inspect the vault

Confirm the quickstart

The quickstart is complete when the vault appears in items with status: "active" and the detail endpoint returns its contract address. A new vault has no shareholder assets until a wallet subscribes. If the authorization reaches rejected, superseded, or expired, correct the reported error and create a new request with a new nonce and idempotency key. If provisioning reports failed, use its error before retrying. Continue with Manage shareholders, Configure strategy, and Subscribe from an external wallet.