Skip to main content
Pick the integration path that fits your stack. SDKs wrap the REST and WebSocket API behind a typed client so you don’t hand-build EIP-712 signatures or envelopes; the raw APIs work from any language.

​
Choose your integration path

Python SDK

Typed client for reads, signed writes, and streams. pip install upside-python-sdk.

REST API

Call POST /exchange and POST /info directly from any language.

WebSocket API

Realtime order book, trades, candles, and per-address account streams.
More language SDKs are on the way.
The Python SDK does not yet cover every endpoint documented here. updateSlippageSetting, accountByAddress, ticker, and the three history queries — userFills, orderHistory, userFundingFlows — have no SDK method yet. Call those over REST directly in the meantime.

​
What every SDK handles

  • EIP-712 signing, no API keys. Writes are authorized by a wallet signature over a fixed domain; the SDK picks the Agent or Typed path and manages nonces. See Authentication.
  • Raw integer prices and sizes. The wire protocol is integer-only — convert display values with each contract’s priceScale / qtyScale from configs; never hardcode a scale.
  • Asynchronous order placement. A submitted order returns status: "accepted" with a count, not the resting order id — read the result from the Info API or the orderUpdates / userFills WebSocket channels.
SDKs default to Devnet (https://dev.upsidemax.xyz). For Mainnet access, contact the UpsideMAX team.