Skip to main content
WEBHOOK
walletActivityMulti
{
  "eventId": "123e4567-e89b-12d3-a456-426614174000",
  "timestamp": "2025-06-01T12:00:00Z",
  "data": {
    "network": "base-mainnet",
    "blockNumber": "12345678",
    "blockTimestamp": "2025-06-01T11:59:55Z",
    "transactionHash": "0xabc123def456789012345678901234567890abcdef1234567890abcdef123456",
    "logIndex": "0",
    "contractAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "eventName": "Transfer"
  },
  "eventType": "wallet.activity.multi"
}

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.activity.multi webhook event payload.

Common fields included in every wallet activity webhook event payload.

eventId
string<uuid>
required

Unique identifier for this webhook event. Use this for idempotency.

Example:

"123e4567-e89b-12d3-a456-426614174000"

timestamp
string<date-time>
required

When this event occurred (ISO 8601 format).

Example:

"2025-06-01T12:00:00Z"

data
object
required

Decoded blockchain event data for the wallet activity webhook. The exact fields depend on the type of onchain activity detected. Common fields include network, block info, and transaction hash. Additional fields are event-specific (e.g., from, to, value for transfers).

Example:
{
"network": "base-mainnet",
"blockNumber": "12345678",
"blockTimestamp": "2025-06-01T11:59:55Z",
"transactionHash": "0xabc123def456789012345678901234567890abcdef1234567890abcdef123456",
"logIndex": "0",
"contractAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"eventName": "Transfer"
}
eventType
enum<string>
required

The type of webhook event.

Available options:
wallet.activity.multi
Example:

"wallet.activity.multi"

Response

Webhook received and processed successfully.