Skip to main content
You want both: data to find edges, execution to act on them. This guide walks the loop end-to-end — discovery, signal, sizing, execution, monitoring — using a single API key across both Predexon products. The loop: 
Discover  →  Signal  →  Size  →  Execute  →  Monitor
(Data API)  (Data API)  (you)   (Trading API)  (WebSocket + Data API)

​
1. Discover

Find the markets you care about. Three common entry points:

By volume

GET /v2/polymarket/markets?sort=volumeTrending markets, ranked.

By search

GET /v2/markets/search?q=...Cross-venue search by question text.

By canonical outcome

GET /v2/marketsPredexon’s normalized outcome view — one predexon_id spans every venue holding it.
For cross-venue arbitrage, matched pairs hands you pre-computed pairs with similarity scores.

​
2. Signal

Find a reason to trade. The signals Predexon gives you out of the box:
SignalEndpointWhat it tells you
Smart-money flow/v2/polymarket/market/{condition_id}/smart-moneyAre profitable wallets net buyers or sellers right now?
Smart activity/v2/polymarket/smart-activityWhich markets are smart wallets piling into?
Top holders/v2/polymarket/markets/{condition_id}/top-holdersPosition concentration on each side.
Wallet P&L/v2/polymarket/wallet/pnl/{wallet}Track-record check before following a wallet.
Cross-venue spreadmatched pairs + market priceSame outcome, different prices — direct arbitrage.
Pending tradesWebSocket pending-trades3–5s edge on confirmed fills, from the Polygon mempool.
For a live edge, subscribe to the WebSocket and react in code. For historical edges, pull from REST and backtest — see the Backtesting section for orderbook replay and signal validation.

​
3. Size

Sizing decisions are yours. The data you’ll usually want before pulling the trigger:

​
4. Execute

Execution goes through venue-specific orders.

Venue-specific order

Place directly on a venue with a market bag. Choose your venue, use native order types, and get a normalized response shape.
Either way, you need an account with funded venues — covered in Trading Quickstart. One account spans every venue you trade on. 
order = requests.post(
    f"{BASE}/api/accounts/{account_id}/orders",
    headers=HEADERS,
    json={
        "venue": "polymarket",
        "market": {"tokenId": token_id},
        "side": "buy",
        "type": "limit",
        "size": "10",
        "price": "0.50",
    },
).json()

​
5. Monitor

Once you have positions, you watch two things: fills and mark-to-market.
WhatWhere
Live fills on your walletWebSocket trades with filters.users: ["<your venue wallet>"]
Live splits / merges / redemptionsWebSocket activity
Live orderbook + best bid/askWebSocket orderbook
Current positions (aggregated)Get Positions on the Trading API
Realized + unrealized P&LWallet P&L on the Data API
The Data API and Trading API share the same wallet addresses, so your venue wallet from GET /accounts/{accountId} plugs straight into any Data API wallet endpoint.

​
Putting it together

Strategies people build with this loop:
  • Cross-venue arbitrage — matched pairs + market price to surface spreads; place each leg with a venue-specific order.
  • Smart-money following — smart-money endpoint or top-holders for entry signals, WebSocket trades to monitor the wallets you’re shadowing.
  • Mempool front-running — pending-trades WebSocket as a leading indicator, venue-specific order with aggressive price.
  • Market-making — orderbook WebSocket for live depth, venue-specific limit orders, fee-policy partner cuts on any fills you take in.

​
Next

Data & Signals overview

Full map of the data side — every endpoint, organized by utility.

Unified Execution overview

Full map of the execution side — accounts, funding, fees.