Skip to main content

HyperCore Info Endpoint Overview

Updated on
May 07, 2026

Overview​

Hyperliquid's Info endpoints provide a comprehensive way to query detailed information about the exchange, user accounts, and market data. These endpoints are designed to fetch real-time data through specific request types, each returning structured data relevant to different aspects of the Hyperliquid ecosystem.

Quicknode's /info endpoint proxies the open-source HyperCore node. 30 of 52 info methods are natively available. The remaining 22 require Hyperliquid Foundation indexer data and are not part of the open-source node.

Method Availability​

MethodAvailableNotes
activeAssetData✅
allMids–Use gRPC TRADES or public HL API
candleSnapshot–Use SQL Explorer or public HL API
clearinghouseState✅
delegations✅
delegatorHistory–Use public HL API
delegatorRewards–Use public HL API
delegatorSummary✅
exchangeStatus✅
extraAgents✅
frontendOpenOrders✅
fundingHistory–Use SQL Explorer or public HL API
gossipRootIps–Use public HL API
historicalOrders–Use public HL API
l2Book–Use gRPC StreamL2Book or public HL API
leadingVaults✅
liquidatable✅
maxBuilderFee✅
maxMarketOrderNtls✅
meta✅
metaAndAssetCtxs–Use SQL Explorer or public HL API
openOrders✅
orderStatus–Use public HL API
outcomeMeta✅
perpDeployAuctionStatus✅
perpDexs✅
perpsAtOpenInterestCap✅
portfolio–Use SQL Explorer or public HL API
predictedFundings–Use public HL API
recentTrades–Use gRPC TRADES or public HL API
referral–Use public HL API
settledOutcome✅
spotClearinghouseState✅
spotDeployState✅
spotMeta✅
spotMetaAndAssetCtxs–Use public HL API
subAccounts✅
tokenDetails–Use public HL API
userFees✅
userFills–Use SQL Explorer or public HL API
userFillsByTime–Use SQL Explorer or public HL API
userFunding–Use SQL Explorer or public HL API
userNonFundingLedgerUpdates–Use public HL API
userRateLimit✅
userRole✅
userToMultiSigSigners✅
userTwapSliceFills–Use public HL API
userVaultEquities✅
validatorL1Votes✅
vaultDetails–Use public HL API
vaultSummaries✅
webData2✅

What are Info Endpoints?​

Info endpoints are specialized API calls that allow you to retrieve various types of data from the Hyperliquid exchange, including:


  • Exchange Metadata: Trading pairs, leverage limits, and margin configurations
  • User Account Data: Open orders, portfolio balances, and trading history
  • Market Information: Order book data, recent trades, and price feeds
  • System Status: Exchange health, maintenance windows, and operational data

Key Features​


  • Real-time Data: Get up-to-date information about markets, orders, and account states
  • User-specific Queries: Fetch account-specific data by providing user addresses
  • Market Data Access: Retrieve order book snapshots, trade history, and price information
  • System Information: Query exchange status, configuration, and operational parameters

Endpoint Configuration​

When you create a Hyperliquid endpoint in the Quicknode dashboard, it comes with /evm at the end by default:

https://your-endpoint.quiknode.pro/evm

For Info endpoints, you need to replace /evm with /info:

https://your-endpoint.quiknode.pro/info

Example Usage​

Here's how to query exchange metadata using the meta info endpoint:

curl https://your-endpoint.quiknode.pro/info \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"type":"meta"}'

This will return comprehensive metadata about the Hyperliquid exchange, including available trading pairs and their configurations.

How Info Endpoints Work​

Info endpoints follow a simple and consistent request-response pattern that makes them easy to use:

Request Structure​

All info endpoints use the same base URL and accept POST requests with a JSON body containing:


  • type (required): Specifies exactly what data you want to retrieve (e.g., "meta", "openOrders", "userFees")
  • Additional parameters: Many endpoints accept optional parameters for:
    • User targeting: Provide a user address to get account-specific data
    • Filtering: Narrow down results by time, asset, or other criteria
    • Configuration: Specify options like market type (perp vs spot)

Example​

# Request: Get exchange metadata

curl https://docs-demo.hype-mainnet.quiknode.pro/info \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"type":"meta"}'


# Response: Structured data about trading pairs and configurations
{
  "universe": [...],
  "marginTables": [...]
}

Refer to the individual endpoint documentation for detailed information on request parameters and response schemas for each specific Info endpoint.

Last updated on
Share this doc