/info API to Uniblock is a two-line change: point at Uniblock’s endpoint and add your API key. Because Uniblock forwards the native /info contract verbatim, every request body and response shape you already use stays the same.
Grab your API key from the
Uniblock dashboard before you start.
What changes
| Public Hyperliquid | Uniblock | |
|---|---|---|
| URL | https://api.hyperliquid.xyz/info | https://api.uniblock.dev/uni/v1/hyperliquid/info?chainId=999 |
| Auth | none | x-api-key: YOUR_API_KEY header |
| Testnet | https://api.hyperliquid-testnet.xyz/info | add chainId=998 |
| Request body | unchanged | unchanged |
| Response body | unchanged | unchanged |
| Rate limits | request-weight cap per IP | no per-IP cap, but plan-level limits apply |
type discriminator, operation-specific fields, and the JSON you get back — is identical.
Before and after
Migrate in code
If you build requests in application code, change the base URL and inject the header once:Python
After migrating
- The public per-IP request-weight cap no longer applies, but keep your retry/backoff logic — Uniblock enforces plan-level rate limits and returns
429when your project exceeds them (backup routing does not bypass this). See Rate Limits & Caching and error codes. - Consider Uniblock’s synthetic types (
portfolioState,batchClearinghouseStates,batchPortfolioStates) to replace multiple round-trips with one request. See the Info API overview. - Using an off-the-shelf Hyperliquid SDK? See SDK Compatibility.