Skip to main content

Overview

The WebSocket channel (beta) delivers real-time payloads as soon as BlockDB finalizes them — ideal for trading, monitoring, or alerting stacks that can’t wait for polling intervals. Events mirror the schemas in the data catalog and preserve _tracing_id so you can reconcile back to archives.
BlockDB WebSocket processing time — end-to-end latency from on-chain finalization to payload delivery.
WebSocket delivery is currently in beta. For issues or throughput requirements, contact support@blockdb.io.

Endpoint & Authentication

Authenticate during the WebSocket handshake using a Bearer token:
If your client cannot send custom headers during the handshake, pass the key as a query parameter:

Quickstart

1) Connect & subscribe

2) Server acknowledgement

3) Live update message

Every data payload follows this envelope:

4) Unsubscribe

Stop a stream without closing the connection:

Available Streams

Subscribe using dataset_id — IDs match the data catalog and REST API identifiers.

Connection Behavior


Full Reference

WSS Introduction

Protocol details: authentication, subscription lifecycle, and message format.

Quickstart

Full code examples in bash, Python, Node.js, Go, .NET, and C.

EVM Streams Overview

Complete stream matrix with links to per-dataset schema pages.

Protobuf (HFT)

Binary-encoded streams for latency-critical and high-frequency trading applications.
Last modified on March 31, 2026