POST
/
api
/
v1
/
developer
/
trading
/
hyperliquid
/
info
HyperLiquid Info Endpoint
curl --request POST \
  --url https://api.allium.so/api/v1/developer/trading/hyperliquid/info \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: <api-key>' \
  --data '{
  "type": "clearinghouseState",
  "user": "0x48cd535b80439fefd6d00f74e5cf9b152adf2671",
  "dex": ""
}'
{}
We offer API endpoints that mirror those of the Hyperliquid API. Please refer to the Hyperliquid API Documentation for the latest parameter details.

Making a request

All requests are made to the info endpoint. With
{"type": [Type]}

Types

activeAssetData

User details regarding an asset:
  • leverage
  • leverage type
  • available to trade
  • mark price

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

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

Response

200
application/json

Successful Response

Response varies based on request type. Can be an object, array, or primitive value depending on the API endpoint called.