Skip to main content
POST
HyperLiquid Info Endpoint
This endpoint provides access to Hyperliquid’s trading data and functionality. This endpoint mirrors the official Hyperliquid API while adding improved error handling.
For the most up-to-date parameter details, refer to the official Hyperliquid API Documentation.

Making Requests

1

Endpoint

Send all requests to the info endpoint
2

Request Format

Use the following JSON structure:
Error Handling DifferenceWhile the official Hyperliquid APIs return a 500 HTTP Status Code for invalid payloads, the Allium Hyperliquid APIs return a 533 HTTP Status Code in these cases for better error differentiation.An unsupported request type or a malformed body returns 422 carrying Hyperliquid’s own message verbatim - Failed to deserialize the JSON body into the target type - which names neither the unsupported type nor the missing field. If a request 422s, check the type against the documented types below and the parameters against each type’s example before suspecting your key: a missing or invalid key is a 403 with {"detail":"Not authenticated"}, never a 422.

Types

activeAssetData

User details regarding an asset:
  • leverage
  • leverage type
  • available to trade
  • mark price
The asset is identified by coin, its name, not by an index. Markets on a HIP-3 builder DEX use the prefixed name and need no dex field of their own, e.g. "coin": "xyz:UNITREE". markPx in the response is market state, not account state: every user address gets the same live mark, including the zero address. A market-level price feed that has no account to ask about can poll with "user": "0x0000000000000000000000000000000000000000" - the mark updates at the venue’s own sub-second cadence.

clearinghouseState

Includes user margin account summaries:
  • positions
  • leverage
  • margin
  • funding paid
  • etc

delegations

delegatorSummary

exchangeStatus

extraAgents

frontendOpenOrders

Includes a user’s open orders details. This is the same call that powers the Hyperliquid Frontend.

leadingVaults

liquidatable

marginTable

Maximum leverage for an asset. Any position below $150,000,000 can use leverage of 40x Any position of $150,000,000 or greater can only use a leverage of 20x.

maxBuilderFee

maxMarketOrderNtls

Maximum notional value allowed for a market order

meta

Metadata regarding perpetual assets
  • Token Name
  • Id
  • Number of decimals
  • Max leverage

openOrders

User’s open orders. Lighter version than frontendOpenOrders

perpDexs

perpDeployAuctionStatus

perpsAtOpenInterestCap

referral

Freshness is ~5s.The following fields are not present in our API response when compared with the Hyperliquid Response.
  • unclaimedRewards
  • claimedRewards
  • builderRewards
For cumVlm you can sum up cumFeesRewardedToReferrer from referralStatesIn addition if the user has not referrer anyone, they will also not show up. If you need to check the referredBy to see if you referred the user, you can check the array of referralStates for your account, and check if the user is in the array.

spotClearinghouseState

Users positions held for spot tokens.

spotDeployState

spotMeta

subAccounts

List a user’s subaccount along with their clearing house state.

userFees

userRateLimit

This rate limit applies only to API endpoints in the api.hyperliquid.xyz

userRole

userToMultiSigSigners

userVaultEquities

webData2

validatorL1Votes

vaultSummaries

votes

Authorizations

X-API-KEY
string
header
required

Body

application/json
type
string
required

Request type, e.g. activeAssetData or clearinghouseState. See the type list for the supported set.

user
string

User's wallet address (hex string). Required by account-scoped types.

dex
string

Builder DEX name for HIP-3 markets, e.g. xyz. Omit for core perps.

coin
string

Asset name, e.g. ETH, or the prefixed name for a HIP-3 market, e.g. xyz:UNITREE. Used by activeAssetData.

id
integer

Margin table id. Used by marginTable.

builder
string

Builder address (hex string). Used by maxBuilderFee.

Response

Successful response