Skip to main content

Hyperliquid gRPC Streaming API

Updated on
Jan 07, 2026

Overview​

Hyperliquid gRPC is a high-performance streaming API that enables real-time blockchain data access through gRPC interfaces. It serves as a powerful tool for developers who need to:

  • Stream blockchain data in real-time
  • Monitor on-chain activities (trades, orders, liquidations, funding events)
  • Query L1 blockchain states efficiently
  • Track TWAP executions and order book changes with minimal latency

The API provides enterprise-grade reliability with granular control over data streams, supporting both L1 HyperCore and L2 HyperEVM data.

Access​

To access Hyperliquid gRPC, you need to have a Quicknode endpoint with gRPC streaming enabled.

Endpoint and Token Configuration​

Hyperliquid gRPC operates on port 10000. This is a dedicated secure port for gRPC communication and is separate from the standard Hyperliquid RPC endpoint. When connecting to the service the port must be specified in the URL:

  • Endpoint: The name of your gRPC-enabled endpoint followed by .hype-mainnet.quiknode.pro and the port number 10000 (e.g., https://example-guide-demo.hype-mainnet.quiknode.pro:10000)
  • Token: Your API key that can be generated from the Quicknode Dashboard Endpoint Security tab.

Given the following example HTTP Provider URL: https://example-guide-demo.hype-mainnet.quiknode.pro/abc123def456/, your authentication credentials would be:

  • Endpoint: https://example-guide-demo.hype-mainnet.quiknode.pro:10000
  • Token: abc123def456

Here is a sample for using this endpoint to connect with Node.js:

const grpc = require('@grpc/grpc-js');
const protoLoader = require('@grpc/proto-loader');
// For HTTP Provider URL: https://example-guide-demo.hype-mainnet.quiknode.pro/abc123def456/
const ENDPOINT = 'example-guide-demo.hype-mainnet.quiknode.pro:10000';
const TOKEN = 'abc123def456';

const client = new hyperliquid.Hyperliquid(ENDPOINT, credentials);
const metadata = new grpc.Metadata();
metadata.add('x-token', TOKEN);

Available Streams​

Stream Type
TRADES
Description
All executed trades with price, size, and direction
Primary Use Case
Trading analytics, price tracking
Stream Type
ORDERS
Description
Order lifecycle events (18+ status types including fills, cancellations)
Primary Use Case
Order management, execution monitoring
Stream Type
BOOK_UPDATES
Description
Order book changes (Level 2 data)
Primary Use Case
Market depth analysis, liquidity monitoring
Stream Type
TWAP
Description
TWAP execution data and algorithm progress
Primary Use Case
Algorithmic trading, execution analytics
Stream Type
EVENTS
Description
System events (funding, liquidations, governance)
Primary Use Case
Risk management, system monitoring
Stream Type
BLOCKS
Description
Raw L1 blockchain data (all transaction types)
Primary Use Case
Blockchain analysis, data archiving
Stream Type
WRITER_ACTIONS
Description
System operations for spot token transfers
Primary Use Case
Cross-environment asset tracking, system monitoring

Stream Filtering​

All Hyperliquid gRPC streams support powerful filtering capabilities to help you receive only the data you need. Filters allow you to focus on specific trading pairs, users, event types, and more, significantly reducing bandwidth and improving performance.

Example gRPC filter:

Subscribe {
  stream_type: TRADES,
  filters: {
    "coin": FilterValues { values: ["BTC", "ETH"] },
    "side": FilterValues { values: ["B"] }
  }
}

Complete Filtering Guide - Detailed documentation with syntax, examples, and field references for all stream types.

Making Hyperliquid gRPC Requests​

To make requests to Hyperliquid gRPC using different languages, check out the resources below:

We ❤️ Feedback!​

If you have any feedback or questions about this documentation, let us know. We'd love to hear from you!

Last updated on
Share this doc