Skip to main content
PATCH
curl
Didit’s wallet update API changes holder metadata and returns refreshed, read-only ownership_proof metadata. The response contains the updated holder fields, label, owner_type, receiving_travel_address and ownership_proof. It is a partial wallet representation. After reassignment, use the returned reuse status instead of assuming an earlier proof still verifies the current holder.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is wrong, revoked or expired; 403 means no key was sent, the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Headers

Idempotency-Key
string

Optional retry-safety key you choose for one operation, up to 255 characters (a UUID works). A request repeated with the same key, endpoint, query and body is answered with the first response, same status and same body, and runs and bills nothing a second time. The same key with another endpoint, query or body returns 409 idempotency_key_reused, and while the first request is still running, 409 idempotency_key_in_progress with Retry-After. A failed request (any 4xx or 5xx) is not stored, so you can send it again with the same key. Keys belong to your application, whether you call with an API key or an access token. See Retries and idempotency.

Required string length: 1 - 255

Path Parameters

entry_uuid
string<uuid>
required

Body

application/json

PATCH is a partial update. The response includes read-only ownership metadata; see WalletAddressEntryUpdateResponse.

holder_name
string
Maximum string length: 255
holder_vendor_data
string
Maximum string length: 255
entity_type
string
Maximum string length: 16
travel_address
string
Maximum string length: 512

Response

The updated entry, including its label, owner type, receiving travel address and ownership proof summary.

Updated holder metadata and read-only ownership metadata. This is a partial wallet representation, not the full list/create entry.

holder_name
string
Maximum string length: 255
holder_vendor_data
string
Maximum string length: 255
entity_type
string
Maximum string length: 16
travel_address
string
Maximum string length: 512
receiving_travel_address
string
read-only

Your per-wallet travel address for this wallet: give it to the sending VASP so its TRP inquiry names this wallet. Empty for a wallet recorded as another VASP's, while Travel Rule is off, and before your VASP profile is saved.

label
string

Current wallet label, exactly as saved.

owner_type
enum<string>

Wallet owner type.

Available options:
customer,
internal,
vasp
ownership_proof
object

Current valid proof, preferring the most recently verified proof; otherwise the latest attempt. A failed retry does not replace a current valid proof. This metadata is read-only.

Example:
Last modified on November 14, 2026