Polymarket runs four order types on its books — GTC, GTD, FOK, and FAK — and not one of them is a stop loss. If you type “polymarket stop loss” into the app’s order panel, nothing happens, because the feature was never built. Traders who want downside protection have to bolt it on themselves, usually through a browser extension, a Telegram bot, or a third-party terminal.
That gap isn’t a bug. It’s a direct consequence of how Polymarket’s exchange is built, and it explains why a small industry of stop-loss tools has popped up around the platform in the last year.
What Polymarket Actually Offers
According to Polymarket’s own trading documentation, every order on the exchange is technically a limit order. GTC (Good-Til-Cancelled) and GTD (Good-Til-Date) orders sit on the book at a fixed price until they fill or expire. FOK (Fill-Or-Kill) and FAK (Fill-And-Kill) are the market-order equivalents — they try to execute immediately against whatever liquidity is sitting on the other side.
None of these four react to price movement on their own. A stop loss, by definition, needs to watch the market and fire an order only after a trigger price is hit. Polymarket’s matching engine doesn’t do that kind of conditional watching — it just matches orders that are already sitting on the book.
We’ve covered the mechanics of one of these order types in more detail in our guide to Polymarket limit orders, which is useful background before trying to automate anything on top of them.
Why a CLOB Makes This Harder, Not Easier
Polymarket’s central limit order book (CLOB) is good for price transparency — you can see exactly what’s resting at each price level. But a CLOB has no built-in concept of “my position” tracking your average entry price and triggering an exit. That logic has to live outside the exchange, in software that watches your wallet and the market simultaneously, then submits a fresh FOK or FAK order when your threshold is crossed.
This is exactly how every stop-loss tool built for Polymarket actually works. A monitoring script checks the current price on a loop, and when it crosses your stop level, it submits a Fill-Or-Kill sell through the CLOB API on your behalf. The order itself is nothing special — it’s the trigger logic wrapped around it that does the work.
How Traders Fake a Stop Loss Today
Three categories of tools have filled the gap:
- Browser extensions that sit on top of the Polymarket web app and let you set a stop and take-profit level per position.
- Telegram bots that monitor your positions server-side and message you, or auto-execute, when a price threshold is hit.
- Trading terminals that bundle stop-loss and take-profit into a full order panel alongside limit orders, built specifically for sports and esports positions where prices move fast around live events.
For readers who trade sports markets specifically, Overdog is one of the terminals that ships this natively — it layers stop-loss and take-profit orders on top of Polymarket’s sports books, which matters because a live NBA or esports market can move 15 points in under a minute and a manually-watched position isn’t fast enough to react.
Whichever tool you pick, the mechanism is the same: software watches the price, then fires a real order through Polymarket’s own API once your level is crossed.
The Catch: These Orders Can Still Fail
A software-triggered stop loss is best-effort, not guaranteed. Three things can break it:
- Thin liquidity. If there isn’t enough size resting on the book at your stop price, a FOK order gets killed entirely rather than partially filled, and a FAK order fills only part of your position.
- Price gaps. A market can jump past your stop level between price checks, especially around a resolution-moving event, leaving you exited at a worse price than intended — or not exited at all.
- Tool downtime. If the bot or extension loses its connection to the API, your stop simply doesn’t fire. Polymarket itself has no record that a conditional order was ever meant to exist.
The practical takeaway: a stop loss on Polymarket is a promise from a piece of software, not a guarantee from the exchange — and that gap is exactly where most trader complaints about “missed stops” come from.
This also means you’re trusting a third party with API access to your wallet or proxy wallet. Before connecting any tool, check what permissions it’s asking for — our breakdown of the Polymarket proxy wallet explains what that wallet can and can’t do if a key gets exposed.
A Simpler Backup: Price Alerts
If you’d rather not hand over API access at all, a lighter option is a price alert that just notifies you, leaving the actual sell order in your own hands. It’s slower than an automated stop, but it keeps full control of execution with you instead of a script. We walked through how to set these up in our guide to Polymarket price alerts.
For small positions or markets that don’t move violently — most political or long-dated economic markets, for instance — an alert plus a manual sell is often enough. For fast-moving sports and live-event markets, the gap between an alert firing and you actually clicking sell is where an automated tool earns its keep.
FAQ
Does Polymarket plan to add native stop-loss orders?
Nothing in Polymarket’s published documentation or order-type roadmap mentions a conditional order type. The four existing order types (GTC, GTD, FOK, FAK) are all that’s documented as of now.
Is using a third-party stop-loss tool against Polymarket’s terms?
These tools submit normal orders through Polymarket’s own public CLOB API — they’re not exploiting anything. The risk is counterparty trust in the tool itself, not a rules violation.
Can I set a stop loss on a position I already hold?
Yes. Every stop-loss tool works off your existing position size and entry price, so you can add protection after the fact rather than only at entry.
