Ir al contenido principal

HyperCore Info Endpoint Overview

Actualizado el
Sep 01, 2026

Resumen​

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 71 of 73 info methods natively. For l2Book y operaciones recientes, Quicknode offers purpose-built gRPC alternatives with better performance than the native info methods.

Method Availability​

MétodoAvailableNotas
activeAssetData✅
allBorrowLendReserveStates✅
allMids✅
allPerpMetas✅
approvedBuilders✅
borrowLendReserveState✅
borrowLendUserState✅
candleSnapshot✅
centro de intercambio de información estatal✅
delegaciones✅
historial del delegador✅
recompensas por delegación✅
resumen del delegador✅
estado del intercambio✅
extraAgents✅
pedidos-pendientes-en-la-interfaz-de-usuario✅
Historial de financiación✅
gossipPriorityAuctionStatus✅
gossipRootIps✅
pedidos históricos✅
isVip✅
l2Book–Use gRPC StreamL2Book (up to 100 price levels, full snapshot per block)
leadingVaults✅
legalCheck✅
liquidable✅
maxBuilderFee✅
maxMarketOrderNtls✅
meta✅
metaAndAssetCtxs✅
pedidos-pendientes✅
estadoDelPedido✅
outcomeMeta✅
outcomeTemplates✅
perpAnnotation✅
perpCategories✅
perpConciseAnnotations✅
perpDeployAuctionStatus✅
perpDexLimits✅
perpDexs✅
perpDexStatus✅
perpsAtOpenInterestCap✅
cartera✅
financiaciones previstas✅
preTransferCheck✅
operaciones recientes–Use gRPC StreamData (TRADES stream) or userFills
derivación✅
Resultado resuelto✅
Estado de la cámara de compensación al contado✅
spotDeployState✅
spotMeta✅
spotMetaAndAssetCtxs✅
spotPairDeployAuctionStatus✅
subcuentas✅
detalles del token✅
twapHistory✅
usdcRouting✅
userAbstraction✅
userBorrowLendInterest✅
userDexAbstraction✅
tarifas de usuario✅
userFills✅
userFillsByTime✅
financiación de los usuarios✅
actualizaciones del libro mayor no relacionadas con la financiación del usuario✅
límite de uso del usuario✅
userRole✅
usuario a firmantes de firma múltiple✅
userTwapSliceFills✅
userVaultEquities✅
validatorL1Votes✅
detalles de la cámara acorazada✅
resúmenes de la cámara acorazada✅
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

Características 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 con /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:


  • tipo (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)

Responses that take a time range will only return 500 elements or distinct blocks of data. To query larger ranges, use the last returned timestamp as the next startTime for pagination.

Ejemplo​

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

Última actualización en