Creating authorization keys
If you are using an authorization key to secure resources controlled by your application server, you can create an authorization key in the Dashboard or locally. During resource creation, specify the public key as the owner.
Keys are required to sign all requests to update a resource. Furthermore, a wallet’s owner is required to sign all requests to take actions with the wallet (POST /v1/wallets/<wallet_id>/rpc).
To create a new authorization key in the Dashboard, visit the Authorization keys page for your app.
Click the New key button and copy and save the generated Private key. Privy does not save this key and cannot help you recover it later. You can also set a human-readable Key name.
In this process, Privy generates a keypair for your app directly on your device, and shows you the private key.
- The private key (e.g. the key you copy) is generated on your device, and is only ever known to your app. Neither Privy nor the secure enclave ever sees the private key, and cannot sign payloads with it.
- The public key is registered with the secure enclave that secures your wallets, and is used to verify signatures produced by your app.
Privy does not store the private key and cannot help you retrieve it.
To create a new authorization key in the Dashboard, visit the Authorization keys page for your app.
Click the New key button and copy and save the generated Private key. Privy does not save this key and cannot help you recover it later. You can also set a human-readable Key name.
In this process, Privy generates a keypair for your app directly on your device, and shows you the private key.
- The private key (e.g. the key you copy) is generated on your device, and is only ever known to your app. Neither Privy nor the secure enclave ever sees the private key, and cannot sign payloads with it.
- The public key is registered with the secure enclave that secures your wallets, and is used to verify signatures produced by your app.
Privy does not store the private key and cannot help you retrieve it.
Authorization keys are P-256 public-private keypairs. Make sure to save the private key, as Privy does not store this and cannot help you recover it.
You can create a keypair with the following command:
Once you have generated your keypair, you can specify the public key in the owner field during resource creation or by updating the resource. You do not need to register it with Privy beforehand.
Creating authorization keys
If you are using an authorization key to secure resources controlled by your application server, you can create an authorization key in the Dashboard or locally. During resource creation, specify the public key as the owner.
Keys are required to sign all requests to update a resource. Furthermore, a wallet’s owner is required to sign all requests to take actions with the wallet (POST /v1/wallets/<wallet_id>/rpc).
To create a new authorization key in the Dashboard, visit the Authorization keys page for your app.
Click the New key button and copy and save the generated Private key. Privy does not save this key and cannot help you recover it later. You can also set a human-readable Key name.
In this process, Privy generates a keypair for your app directly on your device, and shows you the private key.
- The private key (e.g. the key you copy) is generated on your device, and is only ever known to your app. Neither Privy nor the secure enclave ever sees the private key, and cannot sign payloads with it.
- The public key is registered with the secure enclave that secures your wallets, and is used to verify signatures produced by your app.
Privy does not store the private key and cannot help you retrieve it.
To create a new authorization key in the Dashboard, visit the Authorization keys page for your app.
Click the New key button and copy and save the generated Private key. Privy does not save this key and cannot help you recover it later. You can also set a human-readable Key name.
In this process, Privy generates a keypair for your app directly on your device, and shows you the private key.
- The private key (e.g. the key you copy) is generated on your device, and is only ever known to your app. Neither Privy nor the secure enclave ever sees the private key, and cannot sign payloads with it.
- The public key is registered with the secure enclave that secures your wallets, and is used to verify signatures produced by your app.
Privy does not store the private key and cannot help you retrieve it.
Authorization keys are P-256 public-private keypairs. Make sure to save the private key, as Privy does not store this and cannot help you recover it.
You can create a keypair with the following command:
Once you have generated your keypair, you can specify the public key in the owner field during resource creation or by updating the resource. You do not need to register it with Privy beforehand.