Skip to main content

​
Hyperliquid Info API

The Raw Hyperliquid Info endpoint forwards a native Hyperliquid /info request body — selected by its type field — through Uniblock’s unified request lifecycle and returns the upstream response verbatim. Unlike a Direct passthrough, the request flows through the unified provider waterfall, so you get automatic provider failover, billing, and observability while keeping the upstream request and response shapes unchanged.
Remember to create your project & get your API-KEY through our Uniblock’s dashboard.

​
Endpoint

​
Uniblock Query Params

  • chainId: 999 for Hyperliquid mainnet (default) or 998 for Hyperliquid testnet.
  • provider: optionally pin a specific provider; otherwise Uniblock routes through the provider waterfall.

​
How it works

Every request body must include a type discriminator that mirrors Hyperliquid’s own /info contract (for example clearinghouseState, l2Book, metaAndAssetCtxs). The type selects the operation, and any operation-specific fields are forwarded verbatim. Requests without a supported type fail fast with a 400 at the HTTP boundary rather than reaching a provider.

​
Synthetic Uniblock types

In addition to the native Hyperliquid operations, Uniblock defines a set of synthetic types that are composed on Uniblock’s side and dispatched through this same route: Batch types carry a { "type": ..., "users": string[] } body and are limited to 50 users per request.

​
Providers

The following providers serve Raw Hyperliquid Info, in priority order:
  • Alchemy
  • Dwellir
  • Chainstack
  • GoldRush (Covalent)
Provider support is per-type: raw HyperCore-node passthroughs (Dwellir, Chainstack) forward every native node operation, while some aggregations are served only by specific providers. Uniblock routes each request to a provider that serves the requested type.

​
Basic Request

Replace API_KEY with your actual Uniblock API key.

​
Synthetic Portfolio State

Replace API_KEY with your actual Uniblock API key.