Authorization keys provide an additional layer of security for actions taken by your app’s wallets. These cryptographic keys help ensure that only actions explicitly authorized by your server are executed on user wallets.
When you specify an owner
of a resource, all requests to update that resource must be signed with the associated key. Requests to take actions with a wallet must also be signed by the wallet’s owner. This security measure verifies that each request comes from authorized actors.
Resources can be owned by a user or directly by an authorization key.
If you are securing resources controlled by your application server, authorization keys are optional, though strongly recommended.
Authorization keys are particularly important when:
Create authorization keys locally or via the Dashboard and configure this key as the owner
of your resource (e.g. a wallet or policy). See our SDK integration guide or REST API documentation for detailed implementation instructions for signing requests.
Authorization keys provide an additional layer of security for actions taken by your app’s wallets. These cryptographic keys help ensure that only actions explicitly authorized by your server are executed on user wallets.
When you specify an owner
of a resource, all requests to update that resource must be signed with the associated key. Requests to take actions with a wallet must also be signed by the wallet’s owner. This security measure verifies that each request comes from authorized actors.
Resources can be owned by a user or directly by an authorization key.
If you are securing resources controlled by your application server, authorization keys are optional, though strongly recommended.
Authorization keys are particularly important when:
Create authorization keys locally or via the Dashboard and configure this key as the owner
of your resource (e.g. a wallet or policy). See our SDK integration guide or REST API documentation for detailed implementation instructions for signing requests.