Kalshi Order Types During a Price Spike: What a One-Minute 17¢ → 90¢ → 17¢ Swing Does to Your Limit Orders

    Kalshi's retail app supports two order types — Quick Order and Limit. Neither is a stop-loss. Here's what each actually does when a thin-liquidity market prints a fast price swing, and what to watch for on the order book.

    Last verified: 2026-04-23
    Next audit: 2026-05-07
    Primary source: help.kalshi.com
    Kalshi — CFTC DCM + DCO
    Verbatim citations pending direct verification

    What this page is — and is not

    • Cites help.kalshi.com verbatim for every mechanism claim.
    • Not trading advice. Not a recommendation to use any order type. Not a guarantee about how any specific market behaves.
    • Does not name specific markets, tickers, or dollar amounts from community reports. Illustrative numbers only.

    The 30-second answer

    Kalshi's retail web and mobile app supports two order types — a Quick Order (fill at best available now) and a Limit Order (fill only at your price or better). There is no native stop-loss, stop-limit, or stop-market order type exposed in the retail UI. The FIX/API layer lists Limit (OrdType=2) as the retail-exposed order type, with time-in-force modes Day / GTC / IOC / FOK / GTD. A fast price swing — 17¢ to 90¢ and back in under a minute — does not activate any 'trigger' on Kalshi, because no trigger-based order type exists for retail. A resting limit-sell at 45¢ fills the moment a buyer at 45¢ or higher crosses the book on the way up.

    1. What order types does Kalshi support for retail?

    Quick Order

    Retail

    Fills at the best available price in the order book right now.

    Limit Order

    Retail

    Fills only at your specified price or better. For a buy, that is your limit price or lower. For a sell, that is your limit price or higher.

    Stop-loss / Stop-limit / Stop-market

    Not in retail UI

    Not available in Kalshi's retail web or mobile app as of the last verified date. Kalshi's help center articles 13823811, 13823813, 13823815, and 13823828 describe only Limit (and the Quick Order fill-now wrapper).

    Retail order-type flags are sourced from the verified platform dataset (not hardcoded on this page): market, limit. Mechanism claims cite help.kalshi.com articles 13823811, 13823813, 13823815, and 13823828 verbatim.

    2. What happens when a price prints 17¢ → 90¢ → 17¢ in a minute?

    Illustrative only

    The 17¢ → 90¢ → 17¢ swing below is a mechanism frame, not a claim about any specific contract, ticker, or community-reported dollar amount. The point is to show what each resting order does, not to describe a real trade.

    Book state at start

    Market resting around YES=17¢. Thin book above: a handful of sell offers at 20¢, 25¢, 35¢, 45¢, 60¢, 90¢.

    The trigger

    A large marketable buy sweeps every resting sell offer up to 90¢ in one tick. The last-traded price prints at 90¢. Market-makers replenish offers; price mean-reverts to 17¢ within the minute.

    Order A

    Limit buy YES at 18¢

    Outcome: Untriggered, still rests

    Why: A buy limit at 18¢ needs a seller willing to sell at 18¢ or lower. Nothing in the sweep forced that; the sweep went up, not down.

    Order B

    Limit sell YES at 45¢

    Outcome: FILLED at 45¢ during the upward sweep

    Why: Per help.kalshi.com: Kalshi will execute the purchase of those contracts when a trader is willing to buy at your price or higher. When the sweep crossed 45¢, Order B was the next resting offer at that tier.

    Order C

    Limit sell YES at 50¢

    Outcome: FILLED at 50¢ (Order B ahead in queue cleared first)

    Why: Once the sweep cleared Order B's 45¢ tier, the next resting sell at 50¢ was next in line. The sweep continued upward, filling 50¢, then 60¢, then 90¢.

    Key takeaway

    There is no 'look-through' or time-weighted gate. A resting limit fills the moment the book trades through it, regardless of whether the swing reverses one second later.

    3. Does a "sell if YES=45%" limit order trigger on a brief tick?

    User frame: I set my Kalshi order to sell if YES hits 45%.

    Actual mechanism: Kalshi's retail app does not offer a 'sell if' trigger. What you most likely did was place a Limit Sell at 45¢. That order is resting on the book from the moment you submit it. It fills as soon as any buyer at 45¢ or higher crosses the book, even if the last-trade ticker touched that price for only a fraction of a second.

    Consequence: If the book trades through 45¢ on the way up and then retraces, your order is already filled. You cannot 'cancel after the fact' because the trade printed first.

    Source: help.kalshi.com/en/articles/13823815-limit-order-sale (limit-sell fill behavior)

    4. Is there a native stop-loss on Kalshi's retail app?

    Retail UI: As of the last verified date, neither the Kalshi web app nor the iOS/Android retail app exposes a native stop-loss, stop-limit, or stop-market order type. The help-center articles 13823811 / 13823813 / 13823815 / 13823828 describe only Limit and the Quick Order wrapper. No 'Stop' tab, 'Trigger' field, or 'If-then' order builder exists in the retail UI.

    FIX / API layer: The public FIX order-entry reference at docs.kalshi.com/fix/order-entry lists OrdType=2 (Limit) as the retail-exposed value; Stop-type OrdType values are not documented as retail-exposed.

    Community history: r/Kalshi threads from Nov 2024 and Dec 2024 have requested stop-loss functionality. No retail stop-loss has been announced at time of publish.

    If Kalshi ships a retail stop-loss, stop-limit, or trigger-order type, this page must update same-day. Re-verify help.kalshi.com articles 13823811 / 13823813 / 13823815 / 13823828 AND docs.kalshi.com/fix/order-entry on every shipped change.

    5. Time-in-force settings that affect execution during a spike

    Day

    Day

    Active until the end of the current trading session. If unfilled at close, the order is cancelled.

    GTC

    Good 'Til Cancelled

    Rests on the book until filled or manually cancelled.

    IOC

    Immediate-or-Cancel

    Fills whatever portion can fill immediately at or better than your price; cancels the rest.

    FOK

    Fill-or-Kill

    Fills the entire order immediately or cancels entirely. No partial fills.

    GTD

    Good 'Til Date

    Rests on the book until a specified cancel date.

    Sourced from news.kalshi.com/p/utilizing-limit-orders and docs.kalshi.com/fix/order-entry. Strictly mechanism, not a recommendation.

    6. Order-book behavior during a thin-liquidity spike

    The order book displays all resting bids and asks at each price level. A marketable order fills against the best-priced resting counter-orders first, then sweeps through deeper levels if the order size exceeds the top of book.

    When there are few resting bids at the next price tier, one large marketable buy can clear 5–10 tiers in a single sweep, printing a 'spike' on the last-trade chart even though only a handful of contracts actually traded.

    Source: help.kalshi.com — The Orderbook

    7. What Kalshi says you can do instead

    Kalshi's own support-and-resistance post uses the phrase 'stop-losses' only as a general trading concept — not as a platform feature. Per Kalshi's utilizing-limit-orders post, workarounds for managing downside on a resting position include:

    • Place a laddered limit-sell stack

      Instead of one sell at 45¢, place smaller sells at 40¢, 45¢, 50¢. A fast sweep fills them in order; a slow drift fills them one at a time.

    • Cancel resting orders before a known-binary event

      If a resolving print is imminent (election call, court ruling, weather cutoff), cancelling resting orders removes the risk of a spike filling them against your intent.

    • Monitor the depth chart, not the last-trade chart

      The last-trade chart shows the price of the last matched contract. The depth chart shows resting liquidity at each tier. A spike on the last-trade chart with thin depth means few contracts actually traded; a wide mid-price gap means a single large order will move the chart further.

    These are user workarounds sourced from Kalshi's own published trading posts. They are not a native stop-loss feature and are not a recommendation.

    Market pause: what happens to resting orders?

    Kalshi's FIX documentation exposes Tag 21006 CancelOrderOnPause. When set, resting orders are cancelled if the market enters a paused state. This is an API-level flag; the retail app default behavior is not spelled out verbatim in the help center as of the last verified date.

    Source: docs.kalshi.com/fix/order-entry

    FAQ

    Our policy on this page

    Editorial restraint applied to this page:

    1. Cite help.kalshi.com verbatim for every mechanism claim. No paraphrase of primary-source rules.
    2. No trading advice. No recommendation to use or avoid any order type.
    3. No named market tickers or dollar amounts from community reports. Illustrative numbers only — the 17¢ → 90¢ → 17¢ frame is a mechanism, not a claim about a specific contract.
    4. Never name the Reddit users whose questions triggered this page.
    5. Never claim Kalshi is broken, gamed, or unsafe because of order-type limitations — describe the mechanism, let the reader decide.
    6. If Kalshi ships a native stop-loss, stop-limit, or trigger-order type for retail, this page must update same-day. Re-verify help.kalshi.com on every shipped change.
    7. Banned as primary: DefiRate, Covers.com, Benzinga, CoinDesk, CoinTelegraph, Wikipedia, Reddit, Medium, and any affiliate site offering 'Kalshi stop-loss guide.' Primary = Kalshi help center, Kalshi news, Kalshi FIX docs.
    8. Tier-1 narrative-frame shifts (e.g. Kalshi announces retail stop-loss, CFTC adds a rule affecting order types) get recorded in a future narrativeShifts[] array, not baked into row rewrites. Rows change only on primary-source evidence.

    Primary sources

    30 affiliate-farm, crypto-press, and secondary-coverage domains are explicitly excluded from this page per the published editorial policy.