Prepares, signs, and sends a user operation for an EVM Smart Account. This API can be used only if the owner on Smart Account is a CDP EVM Account.
A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the Generate Bearer Token section of our Authentication docs for information on how to generate your Bearer Token.
An optional UUID v4 request header for making requests safely retryable. When included, duplicate requests with the same key will return identical responses. Refer to our Idempotency docs for more information on using idempotency keys.
36A JWT signed using your Wallet Secret, encoded in base64. Refer to the Generate Wallet Token section of our Authentication docs for more details on how to generate your Wallet Token.
The address of the EVM Smart Account to execute the user operation from.
The network the user operation is for.
base-sepolia, base, arbitrum, optimism, zora, polygon, bnb, avalanche, ethereum, ethereum-sepolia "base"
The list of calls to make from the Smart Account.
The URL of the paymaster to use for the user operation.
"https://api.developer.coinbase.com/rpc/v1/base/<token>"
The user operation was successfully prepared, signed, and sent.
The network the user operation is for.
base-sepolia, base, arbitrum, optimism, zora, polygon, bnb, avalanche, ethereum, ethereum-sepolia "base"
The hash of the user operation. This is not the transaction hash, as a transaction consists of multiple user operations. The user operation hash is the hash of this particular user operation which gets signed by the owner of the Smart Account.
"0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
The list of calls in the user operation.
[
{
"to": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48",
"value": "0",
"data": "0xa9059cbb000000000000000000000000fc807d1be4997e5c7b33e4d8d57e60c5b0f02b1a0000000000000000000000000000000000000000000000000000000000000064"
},
{
"to": "0xdac17f958d2ee523a2206206994597c13d831ec7",
"value": "1000000000000000",
"data": "0x"
}
]The status of the user operation.
pending, signed, broadcast, complete, dropped, failed "pending"
The hash of the transaction that included this particular user operation. This gets set after the user operation is broadcasted and the transaction is included in a block.
"0x0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
The list of receipts associated with the user operation.
The receipt that contains information about the execution of user operation.
{
"revert": {
"data": "0x123",
"message": "reason for failure"
},
"blockHash": "0x386544b58930c0ec9e8f3ed09fb4cdb76b9ae0a1a37ddcacebe3925b57978e65",
"blockNumber": 29338819,
"gasUsed": "100000"
}[
{
"revert": {
"data": "0x123",
"message": "reason for failure"
},
"blockHash": "0x386544b58930c0ec9e8f3ed09fb4cdb76b9ae0a1a37ddcacebe3925b57978e65",
"blockNumber": 29338819,
"gasUsed": "100000"
}
]