Run a request
1
Choose an endpoint
Start with a low-cost market-state route such as a Hyperliquid order book.
2
Add your API key
Use the
X-API-Key auth control on the endpoint page.3
Run the request
Inspect
success, data, and meta.request_id.4
Copy the code example
Move the same request into curl, Python, JavaScript, or Go. The Quickstart runs the same flow from a terminal.
What the playground is for
Use the playground to confirm route shape, auth, parameters, and response fields before writing code. It is especially useful when you are choosing between route families: compare a Hyperliquid core example, a Spot pair, a HIP-3 namespaced symbol, a HIP-4 outcome, and a Lighter symbol before committing a route to a client. A playground success confirms that one route answers with the key and parameters you gave it; it is not a substitute for production error handling. After you copy an example, add key management, retries, request-ID logging, pagination, limit handling, and data-quality checks wherever downstream use depends on correctness. If a request fails in the browser but the generated curl example works, continue from curl: it shows the exact method, path, parameters, andX-API-Key header, and does not depend on the browser’s auth or CORS environment. If both fail, keep the status, error code, route, parameters, and request ID together before you debug the client.
Test safely
Start with low-cost market-state routes, then move to historical windows. Keep query parameters narrow while testing: one symbol, one route, one time window, and a smalllimit. Once the response is understood, move to the CLI, an SDK, REST code, or OpenAPI codegen for repeatable work.