Skip to main content
Event: market_disputed
Cost: 0.1 credits per delivery
The market_disputed event fires when a proposed market resolution is challenged on-chain (DisputePrice or AssertionDisputed). The resolution is now contested and delayed. The payload carries the disputer, the proposer, and the disputed or proposed outcome when available. The full payload schema is in the auto-generated Market Disputed callback reference; this page documents the filters and matching behavior.

​
When to use this

  • Flag markets whose resolution is contested so you can hold settlement until it clears.
  • Alert users that an outcome they hold is under dispute.
  • Track dispute activity for risk or moderation workflows.

​
Subscription filters

Add these to the filters object when you create the subscription. All filters are optional.
FilterTypeDescription
condition_idsstring[]Restrict to specific markets by condition ID (max 500).
event_slugsstring[]Restrict to specific events by slug (max 500).
exclude_shortterm_marketsbooleanExclude short-term Up/Down markets.

​
Example

{
  "url": "https://your-server.com/webhooks",
  "event": "market_disputed",
  "filters": {
    "exclude_shortterm_markets": true
  }
}

​
Notes

  • dispute_kind reports which oracle event produced the dispute (dispute_price or assertion_disputed).
  • proposed_price is present only for DisputePrice disputes (0.0–1.0).
  • Pair this with market_resolved to follow a market from contested back to final.
Last modified on June 15, 2026