Api reference
Execute Passkey
Execute operations with passkey validation.
Execute operations with passkey validation.
Endpoint
POST /executePasskeyDescription
Executes operations with passkey validation. This endpoint requires passkey signatures that can be obtained from the passkey hash endpoint.
Request Body
{
"operations": [
{
"encodedUserOp": "0x...",
"userOpHash": "0x...",
"validationData": {
"signature": "base64-signature",
"authenticatorData": "base64-data",
"clientDataJSON": "base64-json",
"validAfter": 1718733600,
"validUnitl": 1718733700
}
}
],
"settings": {
"rpc": "https://polygon-amoy.infura.io/v3/{key}",
"entryPoint": "0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789"
}
}Response
Same as Execute Operation endpoint.
Use Cases
- Passwordless transactions: Execute transactions using biometric authentication
- Enhanced security: Combine passkey validation with Account Abstraction
- User-friendly UX: Provide seamless transaction signing experience
- Mobile applications: Leverage device biometrics for transaction signing
Best Practices
- Get passkey hash first: Use passkey hash endpoint to get the hash to sign
- Validate passkey data: Ensure passkey signatures are valid before execution
- Handle time windows: Use validAfter and validUntil for time-based validation
- Error handling: Check for passkey validation errors
Related Endpoints
- Passkey Hash - Get hash to sign with passkey
- Execute Operation - Execute standard operations
✅ Success: Passkey execution provides a seamless, passwordless transaction experience. Users can sign transactions using biometric authentication on their devices.