Wallet transaction pending
Triggered when the wallet.transaction.pending webhook event is emitted. Your API will receive a POST request at the webhook URL you configured.
Authorizations
HMAC-SHA256 signature of the raw request body, computed using your webhook secret. Webhook receivers should always verify this header before processing the event. The header value is hex-encoded and prefixed by the algorithm and timestamp, e.g. t=1700000000,v1=abc123... (refer to the Webhook Security docs for the exact verification algorithm).
This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.
Body
The wallet.transaction.pending webhook event payload.
- API Key Wallet
- User Wallet
- User Wallet (Delegated Signing)
Delivered when a transaction enters the pending state. EVM-only. The payload is one of three EVM wallet-type variants: API Key Wallet, User Wallet, or User Wallet (Delegated Signing).
The onchain transaction hash.
"0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
The EVM wallet address whose transaction is pending.
1 - 128^0x[0-9a-fA-F]{40}$"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"
The blockchain network identifier.
base, ethereum, solana, aptos, arbitrum, arbitrum-sepolia, optimism, polygon, world, world-sepolia "base"
When the transaction entered the pending state (ISO 8601 format).
"2025-06-01T10:04:00Z"
EIP-1559 max fee per gas in wei.
"30000000000"
EIP-1559 max priority fee per gas in wei.
"1500000000"
Response
Webhook received and processed successfully.