API

Hyperliquid REST API

Read positions, orders, and fills for one wallet or 1,000 in a single POST to /info. Builder endpoints such as builderFills sit next to the same clearinghouseState shape as the public API, with far higher limits.

{"type":"clearinghouseState","user":"0x0000...0000"}
View DocsTalk to us

Unique builder endpoints

Endpoints the native API doesn't have — builderFills, builderLiquidations, builder user states. Query everything about your builder in one place.

Batch operations

Query 1000+ wallets in a single call. Stop looping over the native API one address at a time.

Far higher limits

Token-based plans instead of the public API's tight throttling. Your app stays within far higher limits.

Granular market data

Advanced, granular market data with an improved schema — built from feedback from 100+ Hyperliquid builders.

Built from the schema up for Hyperliquid builders

The native Hyperliquid API was built for the exchange, not for the teams building on top of it. We rebuilt the schema around how builders actually query data — batching thousands of wallets into a single request, exposing builder-attributed fills and liquidations the native API never surfaced, and removing the rate limits that force you to architect around throttling.

The result is less glue code, faster ingestion, and a data layer that scales with your app instead of fighting it — the same infrastructure powering 100+ teams across HyperCore.

Example

One wallet or a thousand — same call

Read the full clearinghouse state for a single user with clearinghouseState, or fetch up to 1,000 users at once with batchClearinghouseStates — a Hydromancer endpoint the native API doesn't offer. Same shape, one request, no looping.

clearinghouseState

Complete clearinghouse state for a single user.

request
curl -X POST https://api.hydromancer.xyz/info \
  -H "Authorization: Bearer $HYDROMANCER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "clearinghouseState",
    "user": "0x0000...0000"
  }'
batchClearinghouseStates

Up to 1,000 users in one request — a Hydromancer endpoint the native API doesn't have.

Hydromancerrequest
curl -X POST https://api.hydromancer.xyz/info \
  -H "Authorization: Bearer $HYDROMANCER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "batchClearinghouseStates",
    "users": [
      "0x0000...0001",
      "0x0000...0002"
    ]
  }'
userFillsByTime

A wallet's fills in a time range: 2,000 per response, with a cursor for the next page.

request
curl -X POST https://api.hydromancer.xyz/info \
  -H "Authorization: Bearer $HYDROMANCER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "userFillsByTime",
    "user": "0x...",
    "startTime": 1793000000000
  }'

Our APIs are used by leading teams

Low latency, improved schemas, and proven reliability — because we want you to ship unique features on the best tech stack possible.

View PricingSee who builds on it