Update a wallet
The following functionality exists for wallets reconstituted server-side. More on Privy architecture here
Privy enables you to update the policies and authorization keys for a wallet that is provisioned for server-side access.
Prior to updating a wallet, the wallet must be provisioned for server-side access.
To update an existing wallet, make a PATCH
request to:
Wallets with owner_id
present must provide an authorization signature as a request header.
Body
In the request body, include the following fields:
New policy IDs to enforce on the wallet. Currently, only one policy is supported per wallet.
The P-256 public key of the owner of the wallet. If you provide this, do not specify an owner_id as it will be generated automatically.
The key quorum ID of the owner of the wallet. If you provide this, do not specify an owner.
The key quorum IDs to add as additional signers for the wallet.
Any fields not included in the PATCH
request body will remain unchanged from the original wallet.
Response
If the wallet is updated successfully, the response will include the updated wallet.
Unique ID for the wallet.
Address of the wallet.
Chain type for the wallet.
Updated policy IDs to enforce on the wallet.
The key quorum ID of the owner of the wallet.
The key quorum IDs of the additional signers for the wallet.
Example
A sample request might look like the following:
A successful response will look like the following:
To update an existing wallet, make a PATCH
request to:
Wallets with owner_id
present must provide an authorization signature as a request header.
Body
In the request body, include the following fields:
New policy IDs to enforce on the wallet. Currently, only one policy is supported per wallet.
The P-256 public key of the owner of the wallet. If you provide this, do not specify an owner_id as it will be generated automatically.
The key quorum ID of the owner of the wallet. If you provide this, do not specify an owner.
The key quorum IDs to add as additional signers for the wallet.
Any fields not included in the PATCH
request body will remain unchanged from the original wallet.
Response
If the wallet is updated successfully, the response will include the updated wallet.
Unique ID for the wallet.
Address of the wallet.
Chain type for the wallet.
Updated policy IDs to enforce on the wallet.
The key quorum ID of the owner of the wallet.
The key quorum IDs of the additional signers for the wallet.
Example
A sample request might look like the following:
A successful response will look like the following: