Directly managing user authorization keys via the API is an advanced setting. We recommend using
Privy’s SDKs, which internally manage user authorization keys if applicable.
- KEM (Key Encapsulation Mechanism): DHKEM_P256_HKDF_SHA256
- KDF (Key Derivation Function): HKDF_SHA256
- AEAD (Authenticated Encryption with Associated Data): CHACHA20_POLY1305
- Mode: BASE
authorization_key
is ciphertext and must be decrypted.Authorizations
Basic Auth header with your app ID as the username and your app secret as the password.
Headers
ID of your Privy app.
Body
application/json
The user's JWT, to be used to authenticate the user.
The encryption type for the authentication response. Currently only supports HPKE.
Available options:
HPKE
The public key of your ECDH keypair, in base64-encoded, SPKI-format, whose private key will be able to decrypt the session key.
Response
200 - application/json
Object with authorization key and wallet IDs.