Aperçu

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 supports 50 of 52 info methods natively. For l2Book et Transactions récentes, Quicknode offers purpose-built gRPC alternatives with better performance than the native info methods.

Method Availability

Méthode	Available	Notes
activeAssetData	✅
allMids	✅
candleSnapshot	✅
clearinghouseState	✅
délégations	✅
historique des délégations	✅
récompenses des délégataires	✅
résumé du délégateur	✅
exchangeStatus	✅
extraAgents	✅
frontendCommandesEnCours	✅
Historique du financement	✅
gossipRootIps	✅
commandes antérieures	✅
l2Book	–	Use gRPC StreamL2Book (up to 100 price levels, full snapshot per block)
leadingVaults	✅
liquidable	✅
maxBuilderFee	✅
maxMarketOrderNtls	✅
méta	✅
metaAndAssetCtxs	✅
commandes en cours	✅
statutDeCommande	✅
outcomeMeta	✅
perpDeployAuctionStatus	✅
perpDexs	✅
perpsAtOpenInterestCap	✅
portefeuille	✅
financements prévus	✅
Transactions récentes	–	Use gRPC StreamData (TRADES stream) or userFills
recommandation	✅
résultat définitif	✅
État de la chambre de compensation au comptant	✅
spotDeployState	✅
spotMeta	✅
spotMetaAndAssetCtxs	✅
sous-comptes	✅
détails du jeton	✅
frais d'utilisation	✅
userFills	✅
userFillsByTime	✅
financement par les utilisateurs	✅
Mises à jour du grand livre non liées au financement par l'utilisateur	✅
userRateLimit	✅
rôle de l'utilisateur	✅
userToMultiSigSigners	✅
userTwapSliceFills	✅
userVaultEquities	✅
validatorL1Votes	✅
détails du coffre-fort	✅
résumés du coffre-fort	✅
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

Caractéristiques principales

• 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 méta 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)

Exemple

# 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.