POST
/
4f8d8f4040bdacd1577bff8058438274
/
info
info (exchangeStatus)
curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info \
  --header 'Content-Type: application/json' \
  --data '{
  "type": "exchangeStatus"
}'
{
  "universe": [
    {
      "name": "<string>",
      "szDecimals": 123
    }
  ]
}
The info endpoint with type: "exchangeStatus" retrieves the current status of the Hyperliquid exchange, including information about all available trading assets and their configurations. This endpoint provides essential metadata about the exchange’s operational status and available markets.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

​
Request body

  • type (string, required) — The request type. Must be "exchangeStatus" to retrieve exchange status information.

​
Response

The response is an object containing exchange status information:

​
Exchange status fields

  • universe (array) — List of all available assets on the exchange, each containing:
    • name (string) — Asset name or symbol (e.g., “BTC”, “ETH”, “SOL”)
    • szDecimals (integer) — Number of decimal places used for size precision in trading

​
Asset information

The universe array provides comprehensive information about all tradeable assets:
  • Asset names: Standard cryptocurrency symbols like “BTC”, “ETH”, “SOL”, etc.
  • Size decimals: Precision configuration for order sizes and position calculations
  • Market availability: All assets listed are available for trading on the exchange

​
Example request

Shell
curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"type": "exchangeStatus"}' \
  https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info

​
Use case

The info endpoint with type: "exchangeStatus" is essential for trading applications that need to:
  • Discover all available trading pairs and assets on the exchange
  • Validate asset symbols before placing orders
  • Configure proper decimal precision for order sizes
  • Build dynamic trading interfaces that adapt to available markets
  • Implement asset selection dropdowns or search functionality
  • Check exchange operational status and market availability
  • Initialize trading bots with current market configuration
  • Verify asset support before implementing trading strategies
  • Build market scanners and portfolio management tools
  • Ensure compatibility with exchange-specific asset naming conventions
This endpoint is typically called during application initialization or periodically to stay updated with any changes to available markets and asset configurations on the Hyperliquid exchange.

Body

application/json

Response

200 - application/json

Exchange status information

Current status of the Hyperliquid exchange