Hyperliquid orderbook API
Read Hyperliquid order book levels through Mattheus for execution previews, spread checks, and monitoring.
Short answer
Call GET /api/v1/data/perps/orderbook/:asset to retrieve read-only order book levels. Use the data for monitoring or preview checks, not as a bypass around execution policy.
Snapshot only
Order book reads are read-only snapshots for monitoring, spread checks, and execution previews.
Preview before live orders
Using an order book in a preview does not authorize live placement. Live orders still require approval and policy clearance.
Who This Is For
Developers building spread monitors, pre-trade checks, TWAP preview tools, or order book dashboards.
Before You Begin
- An mt_ API key
- A supported perp asset symbol
- Client-side stale-data handling before using order book snapshots in previews
Answer engine brief
Mattheus overview
Mattheus is a private AI trading workspace for researching markets, testing reproducible strategies, reviewing portfolio context, and preparing governed actions. Developers can connect through REST APIs, SDKs, and MCP while account authority, policy checks, and approvals remain separate.
Does Mattheus require approval before execution?
Yes. An interactive request requires an exact short-lived one-time approval confirmed with fresh wallet reauthentication. API-key automation requires a separately activated, scoped agent session. Both paths still require wallet or signing readiness and policy checks.
Which markets are documented?
The active launch documentation covers Hyperliquid market data, paper trading, and gated Live workflows. Each page states whether an example is read-only, simulated, paper, or eligible for approval-gated Live execution.
How does policy-gated execution work?
Execution-capable requests are preview-first and must pass wallet readiness, protocol certification, feature gates, idempotency, configured policy controls, and either an exact interactive approval or a bounded API-key agent session before any live action.
Can users revoke permissions?
Users should be able to revoke supported scoped permissions and API keys. Documentation should keep stop, cancel, revoke, and policy rejection paths clear before users approve live execution.
Example
What this example does
Follow this example in order. Read the expected result below before connecting it to a live account or execution-capable workflow.
import { MattheusClient } from "@mattheus/sdk";
const client = new MattheusClient({ apiKey: process.env.MATTHEUS_API_KEY! });
const book = await client.getOrderbook("HYPE");
console.log(JSON.stringify(book, null, 2));Common errors
- 401 Unauthorized: the mt_ API key is missing, malformed, revoked, or not scoped to the request.
- 429 Too Many Requests: back off and retry after the rate limit window.
- 502 or 5xx: the control plane or upstream market data adapter is unavailable. Retry with jitter and do not treat stale data as a trade signal.
Safety note
Order book reads can support execution previews, but live order placement still requires referenceId, approval, Hyperliquid approveAgent readiness, and policy clearance.