Intents are an Enterprise feature. Reach out to [email protected] to request
access for your app.
Asynchronous signing
Privy’s wallet API was originally synchronous: a request to use a wallet had to include every authorization signature in that same request. Intents split this into distinct steps, so signatures can be added independently:- Propose an intent that describes the action to perform, such as a transfer, a transaction, or a resource update.
- Sign the intent by adding authorization signatures one at a time from the resource’s owners or signers.
- Privy executes the action automatically once the signatures satisfy the resource’s authorization threshold.
- Without intents (synchronous)
- With intents (asynchronous)
The action and all of its authorization signatures are sent together in a single request.
For the synchronous flow, where signatures accompany the request, see Signing and
RPC.
Supported actions
An intent can propose any of the following actions:Use cases
Queuing user actions
Intents create a window between proposing an action and executing it. Your app can use that window to run additional steps — compliance or risk screening, funding or onramping, or a user confirmation — before the action executes. For example, an app lets a user buy a token with their fiat balance. The app proposes an intent to execute the swap, runs compliance screening while the intent is pending, onramps funds into the user’s wallet, and only then adds the authorization signature to execute. Intents provide a generic way to introduce additional steps into an authorization flow without blocking on a single synchronous request.Organization wallets and approval orchestration
Because signatures can be added asynchronously by different parties, intents are a natural fit for multi-party approvals. Your app can provision wallets for organizations and collect authorization signatures from multiple members of the organization at their convenience. and Privy orchestrates the collected signatures and executes once the threshold is met. This lets your app offer its own white-labeled approval experience—for example, an internal dashboard for a treasury team—without building signature collection or execution orchestration itself.Relationship to manual approvals
Manual approvals is Privy’s Dashboard-native implementation of intents. Team members review and approve intents directly in the Privy Dashboard, secured by biometric or TOTP MFA. Use manual approvals for a ready-made, Dashboard-based approval flow, or use the Intents API to build your own asynchronous signing flow.Next steps
Propose intents
Propose an intent to transfer funds, run a transaction, or update a resource.
Sign intents
Add authorization signatures to execute a proposed intent.
Intent status
Track an intent from proposal to execution.
API reference
Explore the full Intents REST API.