Client namespaces
Across families, SDK
1.12.0 and later also include:
- Account positions:
positionson the Hyperliquid, HIP-3, Lighter, and Robinhood Chain clients, plusaccounts.by_l1(TypeScriptaccounts.byL1) on Lighter mainnet. See Account positions. - Webhooks:
client.webhooksfor endpoints, subscriptions, estimate and dry-run previews, watched addresses, and the delivery log, plus a signature verifier. See Webhook routes. - Market analytics:
cvdandbreadthon the Hyperliquid and HIP-3 clients,oracleon HIP-3,wallets.classifyon Hyperliquid and HIP-3,questionson HIP-4, and a top-levelsymbols.
1.14.0 and later add four datasets included with the Build, Pro, Scale and Enterprise plans:
- Trade intent:
trade_intent(TypeScripttradeIntent) on the Hyperliquid and HIP-3 clients. See Trade intent. - USDC flows:
usdc_flows(TypeScriptusdcFlows) on the Hyperliquid client. See USDC flows. - Breadth above the moving average:
breadth_ma(TypeScriptbreadthMa) on the Hyperliquid and HIP-3 clients. See Moving-average breadth. - Positioning:
positioningon the Hyperliquid and HIP-3 clients. See Positioning.
getOrderbook(symbol) helper should still name the venue family in its configuration or signature.
REST fallback
Call a route directly when you need its exact shape or your runtime has no SDK. Use the same key, response handling, request-ID logging, and data-quality checks as SDK code.Direct REST
Keep request IDs and errors
Market-data responses carrysuccess, data, and meta: lists add meta.count, paged routes add meta.has_more and meta.next_cursor, and each response has a meta.request_id. When an SDK unwraps data, keep the metadata alongside the result so retries, logs, and support requests still have the request ID.
error_code (errorCode in TypeScript), and the request ID with the failed job. If your wrapper hides metadata, add a logging hook so production callers can still recover the request ID.