Skip to main content

Hyperliquid RPC

With Quicknode, you get access to our global Hyperliquid network which always routes your API requests to the nearest available location, ensuring low latency and the fastest speeds.

Hyperliquid Overview

Hyperliquid is a blockchain designed for on-chain trading with speed and fees that approach centralized exchange performance. The architecture consists of two interconnected components:

HyperCore - The on-chain order book engine that manages trade execution and provides market data. HyperCore exposes seven different data streams (trades, orders, book updates, TWAP, events, blocks, and writer actions) through gRPC streaming, JSON-RPC/HTTP, and WebSocket APIs.

HyperEVM - An EVM-compatible execution layer for smart contract deployment and interaction. Developers can launch new asset classes, build trading strategy vaults, create DeFi protocols, and manage digital assets using standard Ethereum JSON-RPC methods. HyperEVM supports all major Ethereum development tools including Foundry, Hardhat, Web3.js, Ethers.js, and Viem.

Both components operate under HyperBFT consensus (based on HotStuff) and use the native HYPE token for transaction fees.

Interacting with Hyperliquid's APIs

Quicknode provides access to both Hyperliquid components through specialized APIs designed for different use cases:

HyperEVM APIs

HyperEVM supports standard Ethereum JSON-RPC methods, allowing developers to use familiar Ethereum tools like Foundry, Hardhat, and Web3 libraries without modification. Access HyperEVM through two specialized paths:

/evm path - Standard blockchain operations including account balances, transaction queries, smart contract calls (eth_call), gas estimation, and transaction broadcasting. This path is designed for read operations and high-frequency queries.

/nanoreth path - Provides all standard methods plus advanced debugging capabilities (debug_traceTransaction, debug_storageRangeAt), transaction tracing (trace_transaction, trace_block, trace_filter), WebSocket support for real-time blockchain events, and extended historical data archive. This path also supports historical eth_call queries on any block, whereas /evm only supports the latest block.

Compatible with: Foundry, Hardhat, Truffle, Web3.js, Ethers.js, Viem, Metamask, and all standard Ethereum development frameworks.

Due to Hyperliquid's architectural differences, some RPC methods may behave differently from Ethereum. We recommend cross-referencing with the official Hyperliquid documentation for the latest updates.

Cross-layer integration: Smart contracts on HyperEVM can read HyperCore oracle prices. See our guide on accessing HyperCore data from contracts.

HyperCore APIs

HyperCore provides real-time and historical access to exchange data through three API protocols:

JSON-RPC/HTTP (/hypercore path) - On-demand queries for historical exchange data using methods like hl_getLatestBlocks, hl_getBlock, and hl_getBatchBlocks. Fetch up to 200 blocks per request for backfilling data gaps during connection interruptions or batch processing historical trading data.

gRPC Streaming (port 443) - Bidirectional streaming with sub-millisecond latency for market data. Supports all seven data streams with native zstd compression (reduces bandwidth by ~70%). Suitable for market makers, algorithmic trading systems, and real-time analytics applications requiring low latency.

WebSocket (/hypercore path) - Browser-compatible real-time subscriptions using standard WebSocket libraries. JSON-based protocol with hl_subscribe and hl_unsubscribe methods. Supports six data streams (all except BLOCKS, which is gRPC-only). Suitable for web-based trading dashboards, price monitors, and portfolio trackers.

Available Data Streams: TRADES (executed trades), ORDERS (18+ order status types), BOOK_UPDATES (order book changes), TWAP (algorithm execution), EVENTS (balance changes, transfers, liquidations), BLOCKS (raw blockchain data - gRPC only), WRITER_ACTIONS (HyperCore ↔ HyperEVM bridge data).

All streams support filtering by user addresses, trading pairs, order sides, event types, and more. Filter limits vary by plan tier.

Learn more about HyperCore data streams and filtering.

Make Hyperliquid API Calls

To start building on Hyperliquid, create a Quicknode endpoint and access both HyperEVM and HyperCore services.

Quicknode provides managed Hyperliquid infrastructure, giving you access to both components without running your own nodes. These endpoints offer:

  • Reliability - Globally distributed infrastructure to minimize downtime
  • Performance - Low latency and request handling for production applications
  • Dual-component access - Single endpoint provides access to both HyperEVM (smart contracts via /evm and /nanoreth) and HyperCore (exchange data via /hypercore HTTP/WebSocket and gRPC)
  • Multiple protocols - HTTP, WebSocket, and gRPC streaming support
  • Ecosystem integration - Additional functionality through APIs (add-ons) on the Quicknode Marketplace and products like Streams

Visit the QuickStart page to create your endpoint and send your first request.

Supported Networks

Quicknode provides access to the following Hyperliquid networks:

Mainnet
Type:Production
Chain ID:
999
HTTP:
WSS:
Archive:Partial
Pruning:See comment below*
Testnet
Type:Testnet
Chain ID:
998
HTTP:
WSS:
Archive:No
Pruning:pruned to last 250 blocks

*HyperEVM Data Availability:

/evm - Partial historical data; availability varies based on Hyperliquid's peering model. Designed for standard queries on recent blocks.

/nanoreth - Extended historical archive with full tracing support. Includes all debug and trace methods plus WebSocket functionality.

HyperCore Data Availability:

/hypercore (HTTP) - Historical block queries via JSON-RPC methods (hl_getLatestBlocks, hl_getBlock, hl_getBatchBlocks)

/hypercore (WebSocket) - Real-time streaming for 6 data streams (TRADES, ORDERS, BOOK_UPDATES, TWAP, EVENTS, WRITER_ACTIONS)

:10000 (gRPC) - Real-time streaming for all 7 data streams with zstd compression support (includes BLOCKS stream)


Quick Reference

HyperEVM: /evm (HTTP only) • /nanoreth (HTTP + WebSocket + tracing/debugging)

HyperCore: HTTP (historical queries) • WebSocket (6 streams) • gRPC (7 streams + compression)

Learn more about HyperEVM and HyperCore endpoints

Share this doc