Skip to main content
Event: position_volume_spike
Cost: 0.2 credits per delivery
The position_volume_spike event fires when a position’s volume in a timeframe exceeds its recent baseline by your spike ratio. The full payload schema is in the auto-generated Position Volume Spike callback reference; this page documents the filters and matching behavior.

​
When to use this

  • Detect activity surges on a single outcome token rather than a whole market.
  • Tune sensitivity by setting how far volume must exceed its baseline.
  • Scope alerts to specific outcomes or markets you track.

​
Subscription filters

Add these to the filters object when you create the subscription.
FilterTypeDescription
spike_rationumberVolume must exceed its baseline by at least this ratio (must be greater than 1.0).
window_secsintegerLook-back window in seconds (1–600).
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).
timeframesstring[]One or more windows: 1m, 5m, 30m, 1h, 6h, 1d, 24h, 7d, 30d, lifetime.

​
Example

{
  "url": "https://your-server.com/webhooks",
  "event": "position_volume_spike",
  "filters": {
    "spike_ratio": 4.0,
    "window_secs": 180,
    "outcomes": ["Yes"],
    "timeframes": ["1h"]
  }
}

​
Notes

  • spike_ratio must be greater than 1.0; for example 3.0 means 3x the recent baseline.
Last modified on June 3, 2026