Authorizations
Basic Auth header with your app ID as the username and your app secret as the password.
Headers
ID of your Privy app.
Body
New policy IDs to enforce on the wallet. Currently, only one policy is supported per wallet.
1The owner of the resource. If you provide this, do not specify an owner_id as it will be generated automatically. When updating a wallet, you can set the owner to null to remove the owner. The P-256 public key of the owner of the resource, in base64-encoded DER format. If you provide this, do not specify an owner_id as it will be generated automatically.
The key quorum ID to set as the owner of the resource. If you provide this, do not specify an owner.
Additional signers for the wallet.
Response
Created wallet update intent.
Response for a wallet update intent creation request
Unique ID for the intent
Display name of the user who created the intent
Unix timestamp when the intent was created
ID of the resource being modified (wallet_id, policy_id, etc)
Detailed authorization information including key quorum members, thresholds, and signature status
Current status of the intent
pending, executed, failed, expired, rejected Unix timestamp when the intent expires
WALLET The original wallet update request that would be sent to the wallet endpoint
ID of the user who created the intent. If undefined, the intent was created using the app secret
Current state of the wallet before any changes. If undefined, the resource was deleted and no longer exists
{
"id": "id2tptkqrxd39qo9j423etij",
"address": "0xF1DBff66C993EE895C8cb176c30b07A559d76496",
"chain_type": "ethereum",
"policy_ids": [],
"additional_signers": [],
"owner_id": "rkiz0ivz254drv1xw982v3jq",
"created_at": 1741834854578,
"exported_at": null,
"imported_at": null
}Result of wallet update execution (only present if status is 'executed' or 'failed')

