Skip to main content
PATCH
After calling this endpoint, the previous passkey or PIN used to encrypt the private key will no longer work. Make sure the new encryption is persisted before discarding the old key material.

Authorizations

Authorization
string
header
required

Bearer token — use your secret key (sk_prod_xxx) for server-side calls, or the user's JWT for client-side calls

x-api-key
string
header
required

Your Chipi public API key (pk_xxx)

Body

application/json
externalUserId
string
required

Your application's user identifier

newEncryptedPrivateKey
string
required

The private key re-encrypted with the new passkey or PIN

publicKey
string

Wallet public key (required when the user has multiple wallets)

credentialId
string

The passkey that now encrypts the key (after a migration or a recovery). Omit to keep the stored one. A user JWT may change it only for its own user.

prfSupported
boolean

Whether that passkey derives the key with PRF. Omit to keep the stored value.

authMethod
enum<string>

Omit to keep the stored value.

Available options:
passkey,
pin,
passkey+pin

Response

Encryption updated

success
boolean

Whether the update succeeded