Skip to main content
Event: condition_metrics
Cost: 0.1 credits per delivery
The condition_metrics callback fires when a market’s (condition’s) metrics — volume, fees, transactions — cross your thresholds within a timeframe. The full payload schema is in the auto-generated Condition Metrics callback reference; this page documents the filters and matching behavior.

​
When to use this

  • Surface markets whose volume or fee accrual spikes past a threshold inside a rolling window.
  • Track transaction count or unique-trader growth on a specific set of markets.
  • Power “trending market” alerts driven by short-window activity rather than lifetime totals.

​
Subscription filters

Add these to the filters object when you create the subscription.
FilterTypeDescription
condition_idsstring[]Restrict to specific markets by condition ID (max 500).
min_volume_usdnumberMinimum traded volume in USD.
max_volume_usdnumberMaximum traded volume in USD.
min_feesnumberMinimum fees accrued in USD.
min_txnsintegerMinimum transaction count.
min_unique_tradersintegerMinimum number of unique traders.
timeframesstring[]One or more windows: 1m, 5m, 30m, 1h, 6h, 24h, 7d, 30d, lifetime.

​
Example

{
  "url": "https://your-server.com/webhooks",
  "event": "condition_metrics",
  "filters": {
    "min_volume_usd": 50000,
    "min_unique_traders": 25,
    "timeframes": ["1h", "24h"]
  }
}

​
Notes

  • timeframes selects which rolling windows are evaluated; the event fires when the thresholds are met in any listed window.
  • Omitting condition_ids evaluates the thresholds across all markets.
Last modified on June 3, 2026