Skip to main content
GET
/
v2
/
matching-markets
Get Matching Markets
curl --request GET \
  --url https://api.predexon.com/v2/matching-markets \
  --header 'x-api-key: <api-key>'
{
  "query": {
    "condition_id": "<string>",
    "market_slug": "<string>",
    "market_id": "<string>",
    "title": "<string>",
    "status": "<string>",
    "platform": "POLYMARKET"
  },
  "matches": {},
  "summary": {
    "total_matches": 123,
    "exact_matches": 123,
    "related_matches": 123,
    "platforms": [
      "<string>"
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.predexon.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Find matching markets across prediction market platforms. Given a Polymarket identifier (condition ID, market slug, or market ID), a Kalshi market ticker, a Limitless slug, a Predict identifier, or an Opinion identifier, discover equivalent or related markets on the other platforms. Predict and Opinion can be queried by market_id, condition_id, or token_id. They can also be returned when a Polymarket, Kalshi, or Limitless query has verified canonical equivalents.
Provide exactly one identifier parameter, not multiple.
LLM-Based Matching: Market matching is powered by large language models (LLMs). There is a small percentage of markets where hallucinations may occur, resulting in invalid or incorrect matches. Always verify matches before making trading decisions.

​
Match Types

Exact Matches

Same underlying event with equivalent or near-equivalent resolution criteria. Similarity score >= 95.

Related Matches

Similar or correlated events (same entity different outcome, or same event different candidate). Similarity score between 80 and 95. Currently available for Polymarket, Kalshi, and Limitless anchors.

​
Status Values

StatusDescription
activeMarket is open for trading
closedMarket is closed/resolved
The similarity field may be null for matches created before January 4th, 2025.

​
Predict and Opinion Matches

When canonical equivalents exist, the response can include matches.PREDICT.exact and matches.OPINION.exact. Predict and Opinion can also be used as the query anchor. These blocks intentionally expose only execution identifiers and a title:
FieldDescription
market_idVenue-native market ID
condition_idVenue-native condition ID, when available
token_idVenue-native YES token ID, when available
titleVenue-native market title
Predict and Opinion matches do not include side, status, similarity, or explanation in this endpoint. Legacy Polymarket, Kalshi, and Limitless matches retain their existing fields.

Authorizations

​
x-api-key
string
header
required

Query Parameters

​
polymarket_condition_id
string | null

Polymarket condition ID (hex hash)

​
polymarket_market_slug
string | null

Polymarket market slug

​
polymarket_market_id
string | null

Polymarket market ID (numeric)

​
kalshi_market_ticker
string | null

Kalshi market ticker

​
limitless_slug
string | null

Limitless market slug

​
predict_market_id
string | null

Predict market ID

​
predict_condition_id
string | null

Predict condition ID

​
predict_token_id
string | null

Predict YES token ID

​
opinion_market_id
string | null

Opinion market ID

​
opinion_condition_id
string | null

Opinion condition ID

​
opinion_token_id
string | null

Opinion YES token ID

​
match_type
enum<string> | null

Filter by match type: 'exact', 'related', or 'all' (default: all) Match type filter for cross-platform market matching.

Available options:
exact,
related,
all

Response

Successful Response

Response for Polymarket market matching query.

​
query
PolymarketQueryInfo · object
required

Polymarket query information.

​
matches
Matches · object
required
​
summary
MatchSummary · object
required

Summary of matches.