Glossary
Find definitions for the market, trading, identity, clearing, and API terms used throughout the UDX REST and WebSocket documentation.
UDX uses the same terms across REST, WebSocket, and FIX.
| Term | Definition |
|---|---|
| Account | A position-bearing account under one member. |
| API Key | A credential issued for programmatic access on behalf of a user, with explicit scopes and an optional restriction to one account. |
| Contract | The unit traded in a market. One YES contract pays $1 when the market resolves YES and $0 when it resolves NO. Quantities can use increments of 0.01. |
| DCM | Designated Contract Market. The exchange side of UDX that lists markets, runs order books, and matches orders into trades. |
| DCO | Derivatives Clearing Organization. The clearing side of UDX that holds positions and balances and settles markets. |
| Event | A real-world proposition with a binary YES or NO outcome. It is the proposition, not merely a scheduled fixture. |
| Grant | A user’s authorization to act on one specific account belonging to that user’s member. |
| Idempotency Key | An optional client-generated token on a mutating request. Resending an identical keyed request replays the original response rather than executing again; omitting it provides no UDX duplicate/replay protection. Reusing a key with a different request is rejected. |
| L1 | Top-of-book market data: best bid and ask with aggregate size, plus last-trade information. |
| L2 | Market-by-price data: the full price ladder with quantity aggregated at each level. |
| L3 | Market-by-order data: every individual resting order and its queue position. |
| Market | A tradable binary contract whose result is based on one or more event outcomes. Each market has one order book. |
| Market Data | Published views of a market’s order book and trading activity at L1, L2, or L3 depth. |
| Member | A participant that owns users and accounts. REST request capacity is shared at the member level. |
| Order | An instruction to buy or sell YES contracts in one market at specified terms. Resting orders make up its order book. |
| Order Book | The resting buy YES and sell YES orders for a market, organized by price and queue position. |
| Outcome | The resolved YES or NO result of an event. |
| Position | An account’s signed net quantity of YES contracts in a market: positive is long and negative is short. |
| Quote | A single-sided bid or offer answering an RFQ. |
| Resolution | Determining a market’s result from the outcome of its event or events. Resolution occurs before settlement. |
| RFQ | A request for quote: a solicitation for quotes in one market or a set of legs. Its raiser is disclosed to recipients as requester_id, an RFQ participant ID. |
| RFQ Participant ID | The stable pseudonymous identifier a user is known by to RFQ counterparties. GET /users/me returns your own value as rfq_participant_id; it appears on RFQs as requester_id, and quotes carry both the RFQ’s requester_id and the submitter’s quoter_id. |
| Series | A group of related markets created from the same recurring format. |
| Settlement | Applying a resolved market result to positions and crediting the winning side. |
| Trade | An execution created when compatible buy and sell orders match. |
| Transfer | An atomic movement of funds between two accounts of the same member. |
| User | A human or programmatic identity that authenticates and acts for a member through one or more grants. |
| YES Contract | The single contract traded in a market. Buying goes long YES; selling goes short YES. There is no separate NO contract. |