developers:predictionmarkets

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
developers:predictionmarkets [2026/08/27 16:33] – [Example: Won (Short Position, Settles at 0)] chrisdevelopers:predictionmarkets [2026/08/27 19:07] (current) – chris
Line 1: Line 1:
-====== THIS PAGE IS UNDER CONSTRUCTION ====== 
- 
- 
- 
 ====== Prediction Markets ====== ====== Prediction Markets ======
  
Line 47: Line 43:
 **Note:** Settlement messages are generated by the platform and do not represent a resting order in the book. They will not appear in the order book feed and should be treated as system-generated close events. **Note:** Settlement messages are generated by the platform and do not represent a resting order in the book. They will not appear in the order book feed and should be treated as system-generated close events.
 </WRAP> </WRAP>
- 
-===== WebSocket API ===== 
- 
-Settlement is communicated via the standard order update message on the Trading API WebSocket feed. Subscribe to the account feed and watch for order updates matching the criteria above. 
- 
-For full message field definitions see [[developers:websocket:messages|Message Reference]] and [[developers:websocket:orders|Order Routing]]. 
- 
-==== Example: Won (Long Position, Settles at 1) ==== 
- 
-The following is an example order update received when a long position of 1 contract settles in the money. 
- 
-<code javascript> 
-// [TBD -- WebSocket order update JSON/Protobuf example] 
-// Fields to highlight: 
-//   side:       Sell 
-//   price:      1 
-//   order_type: [TBD settlement type] 
-//   qty:        1 
-//   status:     [TBD] 
-</code> 
- 
-==== Example: Lost (Long Position, Settles at 0) ==== 
- 
-<code javascript> 
-// [TBD -- WebSocket order update JSON/Protobuf example] 
-// Fields to highlight: 
-//   side:       Sell 
-//   price:      0 
-//   order_type: [TBD settlement type] 
-//   qty:        1 
-//   status:     [TBD] 
-</code> 
- 
-==== Example: Won (Short Position, Settles at 0) ==== 
- 
-<code javascript> 
-// [TBD -- WebSocket order update JSON/Protobuf example] 
-// Fields to highlight: 
-//   side:       Buy 
-//   price:      0 
-//   order_type: [TBD settlement type] 
-//   qty:        1 
-//   status:     [TBD] 
-</code> 
  
 ===== FIX API ===== ===== FIX API =====
Line 100: Line 52:
 ==== Key FIX Tags ==== ==== Key FIX Tags ====
  
-^ Tag ^ Field Name   ^ Settlement Value ^ +^ Tag ^ Field Name        ^ Settlement Value ^ 
-| 35  | MsgType      | 8 (Execution Report) | +| 1   | Account            | Account holding the position being settled | 
-| 39  | OrdStatus    | [TBD] | +| 8   | BeginString        | FIX protocol version in use | 
-| 54  | Side         | Opposite of open position (1=Buy, 2=Sell) | +| 9   | BodyLength         | Number of bytes in message body | 
-| 44  | Price        | 0 or 1 | +| 10  | CheckSum           | Three-digit checksum for message validation | 
-| 40  | OrdType      | [TBD -- settlement order type] | +| 11  | ClOrdID            | Client-assigned order identifier for the settlement order | 
-| 32  | LastQty      | Position size being closed | +| 14  | CumQty             | Cumulative quantity filled so far | 
-| 150 | ExecType     | [TBD] | +| 17  | ExecID             | Unique identifier for this execution | 
-| 55  | Symbol       | Prediction market instrument identifier | +| 21  | HandlInst          | Order handling instruction (automated, no intervention) | 
 +| 31  | LastPx             | Price of the last fill; 0 or 1 for settlement | 
 +| 32  | LastQty            | Position size being closed | 
 +| 34  | MsgSeqNum          | Sequence number of this message in the session | 
 +| 35  | MsgType            | 8 (Execution Report) | 
 +| 37  | OrderID            | Identifier assigned by broker/exchange for the settlement order | 
 +| 38  | OrderQty           | Total quantity of the settlement order | 
 +| 39  | OrdStatus          | Order Status | 
 +| 40  | OrdType            | Order Type | 
 +| 44  | Price              | 0 or 1 | 
 +| 48  | SecurityID         | Identifier for the underlying contract/instrument | 
 +| 49  | SenderCompID       | Identifier of the sending firm/system | 
 +| 50  | SenderSubID        | Sub-identifier of the sending system | 
 +| 52  | SendingTime        | Timestamp the message was sent | 
 +| 54  | Side               | Opposite of open position (1=Buy, 2=Sell) | 
 +| 55  | Symbol             | Prediction market instrument identifier | 
 +| 56  | TargetCompID       | Identifier of the receiving firm/system | 
 +| 59  | TimeInForce        | Duration the settlement order remains valid | 
 +| 60  | TransactTime       | Timestamp of the actual transaction/execution | 
 +| 97  | LocateReqd         | Whether a locate was required (relevant for short positions) | 
 +| 107 | SecurityDesc       | Name of the contract | 
 +| 151 | LeavesQty          | Remaining quantity left to be filled (0 once fully settled) | 
 +| 167 | SecurityType       | Type of instrument (e.g., option) being settled | 
 +| 200 | MaturityMonthYear  | Contract expiration month/year | 
 +| 201 | PutOrCall          | Indicates whether contract is a put or call | 
 +| 204 | CustOrderCapacity  | Capacity in which the order was entered (customer/firm) | 
 +| 207 | SecurityExchange   | Exchange where the contract is listed/settled | 
 +| 447 | PartyIDSource      | Source/type of identifier used for the party | 
 +| 448 | PartyID            | Identifier of the party involved in settlement (e.g., administrator) | 
 +| 452 | PartyRole          | Role of the identified party in the settlement process | 
 +| 453 | NoPartyIDs         | Number of party ID entries included in the message |
 ==== Example: Won (Long Position, Settles at 1) ==== ==== Example: Won (Long Position, Settles at 1) ====
  
  • developers/predictionmarkets.1787848403.txt.gz
  • Last modified: 2026/08/27 16:33
  • by chris