Guide
How to track Polymarket whales (large trades & smart wallets)
20 June 2026 · 6 min read
Large trades on Polymarket are public by design — the market runs on the Polygon blockchain, so every order is observable on-chain. Tracking them is theoretically straightforward. Doing it in real time, filtering noise from genuine signal, and acting on it usefully is where the work actually lives.
What is Polymarket whale tracking?
In the prediction-market context, a "whale" is a wallet placing a significantly larger position than typical for a given market. People track them for a simple reason: a large, well-timed bet occasionally reflects genuine conviction or information that hasn't fully moved the price yet. If you can see that flow before the market adjusts, there may be an edge.
A few caveats matter here. Whales are not a reliable signal on their own — large positions can reflect emotion, poor calibration, or deliberate price manipulation just as easily as they reflect informed views. Whale activity is best treated as one corroborating data point, not as a trade trigger. Nothing here is financial advice.
Why the data is actually public
Polymarket settles trades on the Polygon blockchain using Gnosis's Conditional Token Framework (CTF). Every buy, sell, and position is a transaction on-chain — visible to anyone with a block explorer or an API call, with no special permissions needed.
Polymarket also exposes this through its own APIs. The Data API (data-api.polymarket.com) provides trade history and holder/position data. The CLOB API (clob.polymarket.com) exposes the live order book, including order sizes and timestamps. You can see who bought, how much, and when — just not always who they are in the real world, because wallet addresses are pseudonymous.
This openness is a genuine differentiator for Polymarket versus traditional betting markets, where book positions are opaque.
What's actually hard about it
The data being public doesn't mean it's easy to use. Four things make whale tracking harder than it sounds:
- Defining "whale" dynamically. A large trade in a low-volume market is very different from the same size in a liquid one. Any threshold you hardcode becomes wrong the moment market conditions change.
- Doing it in real time. The CLOB WebSocket gives you a live feed, but you need to write reconnect logic, parse the message schema correctly, and keep it running reliably — before you get to the analysis.
- Wallet reputation takes time to build. Knowing whether a specific wallet has a good track record requires watching it across many markets and resolutions. That's weeks to months of historical data and careful labelling — not a one-shot query.
- Filtering noise. Most large trades are not meaningful. A market maker, a hedger, or a poorly calibrated big spender can all look identical to an informed whale at order time. Signal-to-noise is low without a filtering layer.
Reading whale data from Polymarket directly
For a quick look at recent large trades, the Data API is the starting point. You can query it without authentication for basic trade history. Here's the shape of a call (no key needed at this level):
curl "https://data-api.polymarket.com/trades?limit=50&taker_order_type=MARKET"
That gives you the raw trade log — amounts, prices, timestamps, and pseudonymous wallet addresses. From there you'd filter by size, cross-reference with market volume, and start building wallet histories. It works, but you're writing the signal logic yourself from scratch.
Idmon's whale-flow signals as a shortcut
Idmon maintains a normalised whale-flow layer built on top of the raw Polymarket data — historical wallet tracking, per-market size thresholds, and real-time enrichment. Instead of ingesting and interpreting the raw stream yourself, you query two endpoints:
GET /api/whales/recent— the most recent large-trade activity, normalised and ranked by significance relative to each market's volume.GET /api/whales/stats— aggregated whale-flow metrics: net directional flow, frequency of large trades, and which markets are seeing unusual positioning.
# recent whale activity
curl -H "Authorization: Bearer YOUR_KEY" \
"https://api.idmon.io/api/whales/recent?limit=20"
# aggregated flow stats
curl -H "Authorization: Bearer YOUR_KEY" \
"https://api.idmon.io/api/whales/stats"
Real-time whale alerts: WebSocket and webhooks
Polling works for research. For anything requiring near-instant awareness — a trading system, a Discord alert bot, a dashboard — you want push delivery.
Idmon supports two push modes:
- WebSocket — subscribe to the whale-flow stream and receive events as they happen. Reconnect handling is straightforward; the docs cover the message schema and heartbeat protocol.
- Signed webhooks — configure a URL (including a Discord webhook endpoint) and Idmon will POST signed events to it as large trades land. The payload includes an
X-Idmon-Signatureheader so you can verify authenticity before acting on it.
Pushing whale alerts into a Discord is a common pattern: large trade fires a webhook, a small bot reformats it as a message, traders in the server see it within seconds. The examples repo has a working webhook receiver in Node and Python.
Try it free, no signup. Idmon's /public/* endpoints serve much of the data at 60 requests/min with no key — including market movers and recent signal activity. See the docs for what's available without authentication. For real-time push, whale flow, headroom, and a commercial licence, request a key — you'll be live within a business day.
What whale tracking is not
A few things worth being explicit about:
- Whale activity is not a reliable prediction of outcomes. It's one signal among many, and its predictive value varies substantially by market type, time horizon, and market state.
- Watching public blockchain data is not insider trading — it's the same data block explorers surface. But following positions blindly without your own analysis is still a risk, not a strategy.
- Wallet addresses are pseudonymous, not anonymous. With enough on-chain history it's sometimes possible to infer an entity's identity, but Idmon does not attempt de-anonymisation and does not surface personal data.
FAQ
Can you actually track Polymarket whales?
Yes. Polymarket runs on the Polygon blockchain, so every trade and wallet position is publicly on-chain. Whale tracking means monitoring that data for unusually large orders and watching whether those wallets tend to be right over time. The data is open; the pipeline and the filtering are the hard parts.
What is a Polymarket whale?
Informally: a wallet placing a much larger position than average for a given market. There's no fixed threshold — it's relative to the market's typical trade size and total volume. Whales attract attention because large positions sometimes reflect strong conviction or information, though that's far from a guarantee.
Does whale activity predict outcomes on Polymarket?
Not reliably on its own. Whales can be wrong, poorly calibrated, or intentionally moving prices. Whale flow is a corroborating signal — useful when it lines up with other indicators, not as a standalone trade trigger. Treat it as informational, not as financial advice.
How do I get Polymarket whale data by API?
Idmon exposes /api/whales/recent and /api/whales/stats under https://api.idmon.io. You can also receive real-time whale alerts by WebSocket or signed webhook — for example pushed directly into a Discord server. Free public endpoints (60 req/min, no signup) are available at /public/*; see the docs for the full list.
Is whale tracking on Polymarket legal?
Reading publicly available on-chain data is legal and routine — it's the same data block explorers and researchers use. Polymarket's data APIs are also publicly accessible within their terms. As always, check the laws and platform terms applicable to your jurisdiction before acting on any of it.
Related: Polymarket API · Webhooks vs REST vs WebSocket · API documentation · Idmon overview