{
"contracts_count": 0,
"created_at": "2026-08-07T10:00:00Z",
"event_slug": "btc-above-70k-december-2026",
"filled_volume": "0",
"id": 1420,
"locked": "6.20",
"market": "12",
"market_title": "Will BTC close above $70,000 on 31 Dec 2026?",
"ord_type": "limit",
"origin_locked": "6.20",
"origin_volume": "10",
"price": "0.62",
"quote_currency": "usdc",
"remaining_volume": "10",
"side": "yes",
"state": "wait",
"updated_at": "2026-08-07T10:05:00Z",
"volume": "10"
}MemberOrder
0
"2026-08-07T10:00:00Z"
"btc-above-70k-december-2026"
"0"
1420
"6.20"
"12"
MarketTitle / EventSlug are the order's market context, denormalised onto the order the same way EventSlug/EventTitle are denormalised onto a market.
Without them market is a bare id and nothing else: a client listing a
member's orders can only print "3573", and has no slug to link with (a
market is not addressable on its own — the app routes
/event/{slug}?market={id}). The only alternative is a market read per row,
which is a fan-out over a paginated list for data this handler already
holds in memory.
Omitted when the market's metadata is unknown here (an id that is in
neither the cache nor storage); the row still carries market.
"Will BTC close above $70,000 on 31 Dec 2026?"
limit, market "limit"
"6.20"
"10"
"0.62"
"usdc"
"10"
yes, no "yes"
wait, done, cancel, reject "wait"
"2026-08-07T10:05:00Z"
"10"