Skip to main content
WEBHOOK
walletTransactionConfirmed
{
  "transaction_hash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
  "address": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e",
  "network": "base",
  "confirmed_at": "2025-06-01T10:05:00Z"
}

Authorizations

​
X-Hook0-Signature
string
header
required

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

application/json

The wallet.transaction.confirmed webhook event payload.

Delivered when a transaction is confirmed onchain. The payload is one of six variants: API Key Wallet, User Wallet, or User Wallet (Delegated Signing), each delivered as an EVM or Solana variant.

​
transaction_hash
string
required

The onchain transaction hash.

Example:

"0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"

​
address
string
required

The EVM wallet address that submitted the transaction.

Required string length: 1 - 128
Pattern: ^0x[0-9a-fA-F]{40}$
Example:

"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"

​
network
enum<string>
required

The blockchain network identifier.

Available options:
base,
ethereum,
solana,
aptos,
arbitrum,
arbitrum-sepolia,
optimism,
polygon,
world,
world-sepolia
Example:

"base"

​
confirmed_at
string<date-time>
required

When the transaction was confirmed (ISO 8601 format).

Example:

"2025-06-01T10:05:00Z"

Response

Webhook received and processed successfully.