Account Abstraction RPC
sendUserOp
Learn how to use the sendUserOp JSON-RPC method.
POST
/
#particle_aa_sendUserOp
Understanding sendUserOp
sendUserOp
pushes a structured and signed UserOperation to the network, also handling session keys, sender management, etc. It takes:- Account config object:
name
- string.version
- string.ownerAddress
- string.biconomyApiKey
- (optional), string. Should only be used if you’d like to use a Biconomy Paymaster.
- UserOp object. This should be signed by the user and if applicable, the Paymaster as well.
- Optionally,
sessions
array - Session key object(s).
- Account config object:
Query example
JSON
Authorizations
Basic authentication header of the form Basic <encoded-value>
, where <encoded-value>
is the base64-encoded string username:password
.
Body
application/json
Version of the JSON-RPC protocol, should be 2.0.
The request identifier.
API method being called.
Available options:
particle_aa_sendUserOp
Parameters for sending a user operation.
Was this page helpful?