Skip to main content
The Trade API lets your own program — a trading tool, an AI agent, a dashboard — read and trade updown’s interval markets directly. It is built for speed and for machines: every response follows a published schema, every price is an exact string, and the live feed tells you when you have missed a message.
Market data is public — no key needed. Placing and cancelling orders needs an API key with the Trade permission. Any signed-in account can create one.
Post liquidity, earn rebates. Your resting orders pay no fee. When another trader fills one, you earn 30–40% of the fee they paid. It’s automatic. See Fees and maker rebates.

Base URLs

Your first request

Market data needs no key. List the markets open right now:
Then read that market’s book:
For live updates, open the websocket instead of polling — with your API key it also pushes your own orders, fills and positions.

Conventions

These hold everywhere in the API, REST and websocket alike.
  • Prices are dollar strings on a 1¢ grid: "0.01" to "0.99", always two decimals. A contract pays $1, so a price is also the implied chance.
  • Counts are contract strings with up to two decimals: "20", "2.50", never a number. The smallest size is "0.01"; responses always show two decimals ("20.00").
  • Underlying prices (the price to beat, the settlement price) are decimal strings: "120.7".
  • Times are epoch milliseconds, UTC, as numbers: 1791304200000.
  • Tickers are opaque. A market ticker such as sol-15m-261006-1630-1645 happens to contain its window’s times, but never parse it — read open_ts_ms and close_ts_ms.
  • Responses wrap the resource in a named key ({ "market": … }, { "trades": [ … ], "cursor": … }), so fields can be added later without breaking your parser. Ignore fields you don’t recognise.
  • Errors are { "code": "MARKET_NOT_FOUND", "message": "…" } with a stable code to switch on. See Errors.

Machine-readable specs

Every endpoint and message is generated from the same schemas the server checks its own responses against, so the specs cannot drift from what the server sends.
  • OpenAPI 3.1 (REST): openapi.json
  • AsyncAPI 3.0 (websocket): asyncapi.json
  • For AI agents: llms.txt, and every page is available as Markdown by adding .md to its URL.

Next steps

Markets and windows

Series, windows, statuses, the price to beat and settlement.

Websocket

Live books, tickers, trades and prices on one connection.

Authentication

API keys: test and live, permissions, limits.

Order entry

Place, track and cancel orders; retry safely.

Fees and maker rebates

Resting orders pay no fee and earn up to 40% of the taker fee.