{
"type": "transaction.execution_reverted",
"wallet_id": "r3mbxxfmzsuxxw3guxxha2xx",
"transaction_id": "537e327d-7382-4e61-93e5-0241c72d0793",
"caip2": "eip155:1",
"transaction_hash": "0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890"
}Webhooks
Transaction execution reverted
Fired when a transaction execution reverts on-chain.
WEBHOOK
transaction.execution_reverted
{
"type": "transaction.execution_reverted",
"wallet_id": "r3mbxxfmzsuxxw3guxxha2xx",
"transaction_id": "537e327d-7382-4e61-93e5-0241c72d0793",
"caip2": "eip155:1",
"transaction_hash": "0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890"
}If a
reference_id was provided when the transaction was created via
eth_sendTransaction or signAndSendTransaction,
it is included in the webhook payload for reconciliation.Body
application/json
Payload for the transaction.execution_reverted webhook event.
The type of webhook event.
Available options:
transaction.execution_reverted The ID of the wallet that initiated the transaction.
The Privy-assigned ID for this transaction.
The CAIP-2 chain identifier (e.g., eip155:4217 for Tempo, eip155:1 for Ethereum mainnet).
The blockchain transaction hash.
Developer-provided reference ID for transaction reconciliation, if one was provided.
Response
200
Return a 200 status to indicate that the webhook was received successfully.
Was this page helpful?