POST
/
4f8d8f4040bdacd1577bff8058438274
/
info
info (maxMarketOrderNtls)
curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info \
  --header 'Content-Type: application/json' \
  --data '{
  "type": "maxMarketOrderNtls"
}'
[
  {
    "coin": "<string>",
    "maxNtl": "<string>",
    "maxSz": "<string>"
  }
]
The info endpoint with type: "maxMarketOrderNtls" retrieves the maximum notional values and sizes allowed for market orders across all available assets on the Hyperliquid exchange. This endpoint provides essential trading limits that help prevent excessive market impact and ensure orderly market operations.
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 "maxMarketOrderNtls" to retrieve maximum market order limits.

​
Response

The response is an array of objects containing market order limits for each asset:

​
Market order limit fields

  • coin (string) — Asset symbol (e.g., “BTC”, “ETH”, “SOL”, “AVAX”)
  • maxNtl (string) — Maximum notional value allowed for market orders in USD
  • maxSz (string, optional) — Maximum size allowed for market orders in asset units

​
Understanding market order limits

Notional value limits:
  • Expressed in USD regardless of the asset being traded
  • Prevents single orders from causing excessive market impact
  • Varies by asset based on liquidity and volatility characteristics
Size limits:
  • Expressed in native asset units (e.g., BTC, ETH)
  • May not be present for all assets
  • Provides alternative sizing constraint alongside notional limits
Risk management:
  • Limits protect both traders and the exchange from extreme market movements
  • Larger, more liquid assets typically have higher limits
  • Limits may be adjusted dynamically based on market conditions

​
Example request

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

​
Use case

The info endpoint with type: "maxMarketOrderNtls" is essential for trading applications that need to:
  • Order validation: Ensure market orders comply with exchange limits before submission
  • Risk management: Implement pre-trade risk checks for large orders
  • Trading interface design: Display maximum order sizes in trading forms
  • Order splitting: Break large orders into smaller chunks that respect limits
  • Liquidity analysis: Understand market depth constraints for different assets
  • Automated trading: Configure trading bots with appropriate size limits
  • Portfolio management: Plan large position entries within exchange constraints
  • Market making: Design strategies that respect maximum order sizes
  • Institutional trading: Implement compliance checks for large order flows
  • Order routing: Optimize order execution strategies based on size limits
  • Risk monitoring: Track order sizes relative to exchange maximums
  • Trading education: Inform users about platform trading limits
  • API integration: Validate order parameters before sending to exchange
  • Performance optimization: Avoid rejected orders due to size violations
This endpoint is particularly important for institutional traders, algorithmic trading systems, and any application that handles large order volumes, as it provides the current exchange limits needed to ensure successful order execution and compliance with platform rules.

Body

application/json

Response

200 - application/json

Maximum market order notional values for all assets

List of maximum market order notional values by asset