UMA API: Optimistic Oracle Resolution Data

Query how Polymarket markets are resolved through UMA’s Optimistic Oracle, including proposals, disputes, and final settlement outcomes.

This page is a scaffold. The endpoint reference below has not been filled in yet. Send the endpoint list and this page will be completed to match the other product pages.

Polymarket markets do not settle themselves. When a market’s event concludes, the outcome has to be reported on-chain and accepted before holders can redeem winning shares. Polymarket uses UMA’s Optimistic Oracle for that step, and the Bravado UMA API exposes the resolution lifecycle as queryable data.

Why Bravado over reading the chain

Resolution data exists on-chain, so this is not about access. It is about not having to build an indexer to answer a question every prediction market application eventually has to answer: is this position actually finished?

	Reading the chain yourself	Bravado UMA API
Setup	Index UMA oracle events yourself	Query an endpoint
Assertion state	Decode on-chain events	Returned as data
Dispute tracking	Watch for challenges and votes	Surfaced in the resolution record
Correlation to positions	Map oracle events back to your holdings	Aligned with the same market identifiers as the rest of Bravado

The practical payoff is that a “concluded” event and a redeemable position stop being the same thing in your data model. An application that conflates them will show users balances they cannot access, and book PnL that has not been realised.

Why resolution matters for traders

Resolution is the point where an outcome token stops being a probability and becomes worth exactly $1 or $0. Three things about that transition affect anyone trading or building on Polymarket:

• Timing. A market’s event can conclude well before its outcome is finalized on-chain. Positions are not redeemable during that window.
• Disputes. A proposed outcome can be challenged, which extends the window and introduces the possibility that the initially proposed answer is not the final one.
• Finality. Only after resolution settles can a position be redeemed via POST /v2/trade/positions/redeem.

How UMA resolution works

1. Assertion

   Once the event concludes, a proposer asserts the outcome on-chain and posts a bond backing that claim.

2. Challenge window

   The assertion stays open for a fixed period. If nobody disputes it, it is treated as correct and settles automatically.

3. Dispute (optional)

   Any party may dispute within the window by posting their own bond. A disputed assertion escalates to UMA’s token-holder vote rather than settling on the proposer’s word.

4. Settlement

   The final outcome is written on-chain. Winning outcome tokens become redeemable at $1; losing tokens go to $0.

A market whose event has visibly concluded is not necessarily settled. Always confirm final resolution state before treating a position as realized, an undisputed assertion can still be disputed until its challenge window closes.

Endpoints

Endpoint documentation is pending. In the meantime, resolution-adjacent behaviour that is documented today:

• POST /v2/trade/positions/redeem, redeem winning shares once a market has settled.
• Error reference, includes the 503 / available: false behaviour returned while data is still being processed.

Related

• Trade API, order execution and position management
• Data API, wallet PnL, trade logs, and tax statements
• Polymarket, market coverage and supported features