/v1/wallets/authenticate
endpoint using the user’s JWT and the public key of the ECDH keypair./v1/wallets/authenticate
endpoint. This key will be used to sign the request before it is submitted to the Privy Wallet API. The expiration time of the key is returned in the response.
The /v1/wallets/authenticate
endpoint integrates directly with the JWT-based authentication settings configured in the Privy dashboard. In particular, the JWT is verified according to the registered JWKS.json endpoint. This endpoint uniquely identifies users based on the subject ID (the sub
claim) within the JWT and verifies the JWT is authorized to transact on the wallet.
/v1/wallets/authenticate
contains the following parameters.
privy-authorization-signature
./v1/wallets/authenticate
endpoint with the following parameters.
privateKey
of your ECDH keypair.
authorizationPrivateKey
to sign requests to the Wallet API.
authorizationPrivateKey
, your application can request a transaction via the Wallet API.
Learn how to generate an authorization signature and send a transaction via the Wallet API.
The fastest way to start sending transactions with an authorization signature is via the Server SDK.