Update my wallet

Change the signed-in account's display name, language, avatar, phone number, onboarding state or email. Send only what you want to change. **Changing the email.** Send `email` together with `current_password`. The account becomes unverified until the code sent to the new address is redeemed. The email change and delivery of that code commit together. **Changing the password.** Send `password` together with `current_password`. Knowing the current password is what proves it is really them, rather than an attacker who obtained a token. Once changed, every other session on the account ends — including on their other devices — so anyone who had the old password loses access. The session making the change carries on. A user who has never set a password — an invited colleague setting their first one — does not need to send `current_password`. Only for the signed-in person's own account, with a signed-in session rather than an API key. Requires the `wallets.update` permission.

PATCH
/wallets/me

Authorization

bearer-auth
AuthorizationBearer <token>

The access token returned after a successful sign-in, sent as Authorization: Bearer <access_token>.

It identifies the person and the organization they are working in, and it lasts about fifteen minutes. When it runs out, use their refresh token at POST /auth/refresh-token instead of asking them to sign in again.

In: header

Request Body

application/json

The details to change.

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

curl -X PATCH "https://api.dual.network/wallets/me" \  -H "Content-Type: application/json" \  -d '{    "nickname": "alexf",    "language": "de"  }'
{}
{
  "code": 3,
  "message": "Key: 'limit' Error:Field validation for 'limit' failed on the 'lte' tag"
}

{
  "code": 16,
  "message": "no auth provided"
}

{
  "code": 13,
  "message": "internal error"
}