Skip to main content
Correlated Markets starts from one prediction market and returns events that may become more relevant if that market resolves a certain way. Use it for related-market rails, portfolio ideas, hedge discovery, and thematic search that goes beyond title matching. All endpoints are app-tier: send x-app-id, no user token. Your app’s venue and category exclusions still apply. Closed and resolved markets are left out unless you pass includeResolved: true.

Endpoint map

Expand vs hedge

  • mode: "expand" returns Yes-side events that become more attractive if your thesis is right.
  • mode: "hedge" returns Yes-side events that become more attractive if your thesis is wrong. Hedge results leave out the expand results for the same market and side.

Resolve a market

Use resolve when your app stores venue-native identifiers. It resolves the market, checks whether signals exist, and returns a paginated cascade.
externalId on resolve is not externalIdentifier and not the webhook partner id. 202 means still generating ({ status: "processing" }). If signals do not exist yet, generation starts and the response says so:
Send the same request again after generation finishes.

Use an AGG market id directly

If you already have a venueMarket.id from GET /venue-events or GET /venue-markets, call the cascade endpoint. This path does not resolve identifiers.
limit is capped at 100. Page with the returned nextCursor.

Result shape

Each result is an event-level candidate. Use venueEventId to fetch the event or link to it.

Inspect generated signals

Each market has a set of generated Yes/No signals: short statements about which real-world states become more or less likely if the market resolves a given way. They drive the cascade and connection endpoints. Fetch them to render “why this is related” copy.

Connections without side or mode

connections returns related events for a market without a side or mode. Use it for a single “Related markets” rail on an event page.
Page with nextCursor. Pass includeResolved=true to include resolved and closed markets.

Search by theme

Use query search when the user starts from a theme instead of a market. Results carry market and event status and dates, so you can keep resolved markets out of tradeable recommendations. Set direction to more_likely or less_likely to filter, or balanced: true to mix both in one page.

Building Market Views

Compose discovery and orderbook endpoints into event grids and trading views.

Comparing Venue Prices

Compare matched markets across venues with live midpoint data.