Skip to main content
Event: position_metrics
Cost: 0.1 credits per delivery
The position_metrics callback fires when a position’s (outcome token’s) metrics cross your thresholds within a timeframe. The full payload schema is in the auto-generated Position Metrics callback reference; this page documents the filters and matching behavior.

​
When to use this

  • Catch outcome tokens with surging buy- or sell-side volume inside a rolling window.
  • Alert on sharp price or probability moves on specific positions.
  • Monitor fee accrual, transaction count, or unique-trader growth at the outcome-token level.

​
Subscription filters

Add these to the filters object when you create the subscription.
FilterTypeDescription
position_idsstring[]Restrict to specific outcome tokens by position ID (max 500).
condition_idsstring[]Restrict to specific markets by condition ID (max 500).
outcomesstring[]Restrict by outcome name, e.g. ["Yes", "No"] (max 500).
min_volume_usdnumberMinimum traded volume in USD.
max_volume_usdnumberMaximum traded volume in USD.
min_buy_usdnumberMinimum buy-side volume in USD.
min_sell_volume_usdnumberMinimum sell-side volume in USD.
min_feesnumberMinimum fees accrued in USD.
min_txnsintegerMinimum transaction count.
min_unique_tradersintegerMinimum number of unique traders.
min_price_change_pctnumberMinimum price change, as a percentage.
min_probability_change_pctnumberMinimum probability change, as a percentage.
timeframesstring[]One or more windows: 1m, 5m, 30m, 1h, 6h, 24h, 7d, 30d, lifetime.

​
Example

{
  "url": "https://your-server.com/webhooks",
  "event": "position_metrics",
  "filters": {
    "outcomes": ["Yes"],
    "min_buy_usd": 10000,
    "min_price_change_pct": 5,
    "timeframes": ["1h"]
  }
}

​
Notes

  • timeframes selects which rolling windows are evaluated; the event fires when the thresholds are met in any listed window.
  • min_price_change_pct and min_probability_change_pct are measured over the evaluated window.
Last modified on June 3, 2026