Skip to main content
PUT
/
v1
/
w3s
/
wallets
/
{id}
Update a wallet
curl --request PUT \
  --url https://api.circle.com/v1/w3s/wallets/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "my wallet",
  "refId": "custom_ref_id"
}'
{
  "data": {
    "wallet": {
      "id": "c4d1da72-111e-4d52-bdbf-2e74a2d803d5",
      "address": "0xca9142d0b9804ef5e239d3bc1c7aa0d1c74e7350",
      "blockchain": "MATIC-AMOY",
      "createDate": "2023-01-01T12:04:05Z",
      "updateDate": "2023-01-01T12:04:05Z",
      "custodyType": "DEVELOPER",
      "name": "<string>",
      "refId": "custom_ref_id",
      "state": "LIVE",
      "userId": "ext_user_id_1",
      "walletSetId": "c4d1da72-111e-4d52-bdbf-2e74a2d803d5",
      "initialPublicKey": "3eQoJ3ex6uWX3R8F1THF6Y6oBQwPYpF1X9HBM1gjqw7w",
      "accountType": "EOA"
    }
  }
}

Authorizations

​
Authorization
string
header
required

Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are requred to make a successful request.

Headers

​
X-Request-Id
string

Developer-provided parameter used to identify this request. Useful when communicating with Circle Support.

Example:

"2adba88e-9d63-44bc-b975-9b6ae3440dde"

Path Parameters

​
id
string<uuid>
required

The universally unique identifier of the resource.

Example:

"b3d9d2d5-4c12-4946-a09d-953e82fae2b0"

Body

application/json

Schema for the request payload to update an existing wallet.

​
name
string

Name or description associated with the wallet or walletSet.

​
refId
string

Reference or description used to identify the object.

Example:

"custom_ref_id"

Response

Successfully updated wallet metadata.

​
data
object
required
⌘I