Overview

The service allows external clients to observe transactions across multiple stages of their lifecycle — from initial network ingress through consensus ordering to final execution — and submit transactions directly into the network pipeline. The API is designed for latency-sensitive infrastructure, trading, analytics, and indexing workloads that require fast access to live transaction data before it becomes available through public RPC infrastructure. The /v1/* route family exposes WebSocket and HTTP endpoints for:

• observing incoming transactions
• monitoring consensus-ordered transactions
• consuming post-execution transaction data and events
• submitting transactions directly to the network

All /v1/* payloads are serialized with BCS. Each WebSocket frame contains one complete BCS document with no additional envelope or framing layer.

​

Route catalogue

Server may send WebSocket Ping frames every ~30 s; respond with Pong (most client libraries do this automatically). Slow subscribers whose receive mailboxes stay full are dropped.