Info Requests

All read operations on UpsideMAX 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

POST /info
Content-Type: application/json

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:

POST /info HTTP/1.1
Content-Type: application/json

{"type": "userOrders", "accountId": "5", "marketDeployerId": 1}

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.

`type`	Description	Reference
`configs`	Lists all contracts, their IDs, price/qty scales, and market parameters	/info/configs
`userMarketDeployers`	Returns the market deployer IDs an account is enrolled in	/info/user-market-deployers
`userAccount`	Returns account summary: balances, margin, and position overview	/info/user-account
`userOrders`	Lists all open orders for an account	/info/user-orders
`ordersByIds`	Fetches specific orders by their server-assigned order IDs	/info/orders-by-ids
`ordersByCloids`	Fetches specific orders by client order IDs	/info/orders-by-cloids
`candleSnapshot`	Returns OHLCV candle data for a contract and time range	/info/candle-snapshot
`l2Book`	Returns the current Level 2 order book for a contract	/info/l2-book
`marketState`	Returns current market state: mark, index, and last price plus the funding rate index	/info/market-state
`shareGroupState`	Returns the state of a portfolio margin share group	/info/share-group-state
`userAgents`	Lists agent addresses authorized to act on behalf of an account	/info/user-agents

Example Queries

Get all open orders for account 5:

{
  "type": "userOrders",
  "accountId": "5",
  "marketDeployerId": 1
}

Get the L2 order book for a contract (asset is the contract ID from configs, sent as a string):

{
  "type": "l2Book",
  "asset": "1"
}

Get hourly candles for a contract over the last 24 hours:

{
  "type": "candleSnapshot",
  "asset": "1",
  "interval": "1h",
  "startTime": 1778486400000,
  "endTime": 1778572800000
}

Get contract configuration:

{
  "type": "configs",
  "marketDeployerId": 1
}

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. For example, userOrders returns an object that echoes the query, with the orders in an orders array (order entries abbreviated here):

{
  "type": "userOrders",
  "accountId": "5",
  "marketDeployerId": 1,
  "contractIdFilter": 0,
  "truncated": false,
  "orders": [
    {
      "id": "6",
      "clientOrderId": "0",
      "contractId": 1,
      "orderSide": "B",
      "orderType": "L",
      "timeInForce": "Gtc",
      "price": "50",
      "size": "10",
      "originalSize": "10",
      "status": "Open"
    }
  ]
}

Overview

Authentication

Request Format

Reference

SDKs

Endpoint

Request Structure

Available Query Types

Example Queries

Response Shape

​Endpoint

​Request Structure

​Available Query Types

​Example Queries

​Response Shape

Endpoint

Request Structure

Available Query Types

Example Queries

Response Shape