QuickNode Event Delivery Contract

Overview

Choose Webhooks for template-driven notifications or Streams for programmable, historical, and multi-destination pipelines. Both require authenticity, fast acknowledgement, idempotency, and explicit chain-reorganization behavior.

Prerequisites

• Product choice, chain, network, dataset, and start range
• An HTTPS receiver or approved durable destination
• A secret store, queue, and replay-aware event identity

Authentication

Authenticate event delivery with the generated HMAC security token and verify the signature over the unmodified request bytes before parsing. For Streams, add mTLS when its trust model is required. Keep endpoint tokens and Admin API keys out of receiver configuration because they authenticate different QuickNode surfaces.

Instructions

Step 1: Select Webhooks or Streams