Reading partial success in Kalshi order batches
Batch submission reduces request overhead. Results still need reconciliation for each instruction.
Event contracts and binary outcomes: resolution rules, sources, timing, costs and uncertainty. The examples explain mechanics and do not promise returns.
Batch submission reduces request overhead. Results still need reconciliation for each instruction.
A first API page can look like a complete list. A finished export requires following the cursor chain.
A team login and a subaccount serve different operational purposes. Check the actual permission scope when configuring either.
Post-only adds a placement condition to a limit order. Its outcome depends on the book when the request is processed.
The number of displayed decimals and the valid price grid can differ. Read the selected market's active constraints before submission.
The November 13 filing concerns the relationship between federal and state authority over event-contract trading.
The November 10 report concerns notification procedures and is separate from the CFTC's Arkansas lawsuit.
Identical false flags can have different meanings according to the HTTP result and exchange index.
Settlement records mix cents and fixed-point dollars. Normalize the units before calculating a result.
The request targets one market and asset. The response distinguishes successful cancellations from remaining failures.
The authenticated heartbeat lets a trading client maintain its connection state. A lapse can trigger cancellation of open orders.
Kalshi moves older data from live to historical endpoints. Long-window imports need both sources and the current cutoff.
A trade creates or transfers an outcome-token position. Redemption is the later action that exchanges a resolved position for collateral.
The queue_position_fp field is a fixed-point count based on price-time priority. Treat it as a timestamped order-book observation.
The scheduled_ts field gives the time a change takes effect. Clearing an override restores the parent series fee structure.
A closed market can still await a result. A determined result can be disputed before the finalized REST status.
Polymarket matches orders offchain and settles trades onchain. Its status codes show how far an execution has progressed.
Kalshi’s Create Order V2 API supports two self-trade prevention modes.
Kalshi lets users group orders under a limit on contracts matched in a rolling 15-second window.
The WebSocket sends an order-book snapshot followed by deltas. Kalshi’s seq counts messages on a subscription.
For Polymarket markets using the UMA Optimistic Oracle, a proposed outcome enters a two-hour challenge period. An undisputed proposal is accepted.
In a Polymarket negative-risk event, one No token for an outcome can be converted into one Yes token for each other outcome in the group.
Log loss scores the probability assigned to the actual outcome. If Yes has probability p, the loss is −ln(p) when Yes occurs and −ln(1−p) when No occurs.
Under the CFTC’s electronic trading risk principles, US designated contract markets apply exchange-based pre-trade controls to all electronic orders.