Skip to main content
All read operations on Upside use a single endpoint: POST /info. No authentication is required — you send a JSON body with a type field that identifies the query, along with any query-specific parameters. The server returns the requested data directly in the response body.

Endpoint

Request Structure

Every POST /info body is a JSON object with a top-level type field that routes the request, plus any additional parameters the query requires:
The type field plays the same routing role here that action.type plays for POST /exchange write requests — the URL never changes, and you express intent through the JSON body.

Available Query Types

Cache configs responses client-side. Configuration data — contract IDs, price scales, quantity scales, and market parameters — changes rarely and only when new contracts are listed. Avoid calling configs on every request.

Example Queries

Get all open orders for account 5:
Get the L2 order book for SOL1 (asset 1):
Get hourly candles for SOL1 over the last 24 hours:
Get contract configuration:

Response Shape

A successful /info response returns HTTP 200 with the query result directly in the body. The structure varies by query type — refer to the individual query reference pages linked in the table above.