Full analysis selected. Choose Quick brief to read the key points first.
WFN QUICK BRIEF · UNDER 1 MIN
The short version
MODE 2 OF 2
The documented behavior
Kalshi V2 processes an order batch sequentially in request order. A 201 response has a result for each item, with an identifier for success or an error object for failure. Timeout or unavailable errors can leave placement uncertain. Some preliminary checks reject the entire batch before orders are sent. Kalshi · Batch Create Orders V2 ↗
How a duplicate position arises
Imagine three instructions: the first returns an order ID, the second has invalid parameters and the third has an uncertain outcome. Resending the whole batch risks repeating the first instruction. Instead, map each original intention to its result, correct the rejected one and reconcile the uncertain one. Save local identifiers before submission.
Showing the result to staff
Display the batch's overall progress with a separate state for each row and access to its raw response. Accepted, rejected and unreconciled counts explain the remaining work. Test mixed responses and connection loss after submission. This is especially important for linked positions whose exposure changes when only part of a batch executes.
Quick Brief is a reading aid. The full article and source trail stay on this page.
01 · VERIFIED RECORD
The documented behavior
Kalshi V2 processes an order batch sequentially in request order. A 201 response has a result for each item, with an identifier for success or an error object for failure. Timeout or unavailable errors can leave placement uncertain. Some preliminary checks reject the entire batch before orders are sent. Kalshi · Batch Create Orders V2 ↗
02 · WFN EDITORIAL ANALYSIS
How a duplicate position arises
Imagine three instructions: the first returns an order ID, the second has invalid parameters and the third has an uncertain outcome. Resending the whole batch risks repeating the first instruction. Instead, map each original intention to its result, correct the rejected one and reconcile the uncertain one. Save local identifiers before submission.
03 · REVIEW POINTS
Showing the result to staff
Display the batch's overall progress with a separate state for each row and access to its raw response. Accepted, rejected and unreconciled counts explain the remaining work. Test mixed responses and connection loss after submission. This is especially important for linked positions whose exposure changes when only part of a batch executes.
Original WFN vector illustrationWFN · 22 November 2026
Reading tools and source notes
WFN STORY COMPASS
Choose your reading angle
Switch between the reported record, market context and open questions. Status labels distinguish claims from findings.
All context layers are visible. Choose a lens to jump to that part of the story.
Editorial notePrimary sources and WFN analysis are identified in the article. Cover illustration by WFN.
WFN REALITY LEDGER
What is on the record?
Practical explainer
Practical explainer
Primary record / reference periodKalshi · Batch Create Orders V2