Skip to Content
PredictorSDK

Ambiguous bare identifiers now return 409 instead of the wrong provider's market

BreakingFix

GET /v1/markets/{market_id} and GET /v1/events/{event_id} accept a bare identifier and infer the platform from its shape. Bare numeric ids and kebab-case slugs do not name a platform — Polymarket and Predict both use those shapes — so the service probed Polymarket first and returned whichever provider answered first.

Those id spaces genuinely overlap, so "first to answer" was frequently the wrong provider. Measured against production on 2026-08-25, across 93 Predict market ids taken from our own GET /v1/matching-markets/sports response:

  • 53 of 93 (57%) returned an unrelated Polymarket market with a 200 on it. Predict market 1607914, an Arizona Diamondbacks vs. San Francisco Giants game, came back as "Will Ze-Cheng Dou finish in the Top 5 at the 2026 Valspar Championship?"
  • 57 of 93 (61%) resolved to a different provider on /v1/markets than on /v1/events, because a Polymarket market with that number existed while a Polymarket event with it did not. A caller walking the documented pipeline — matching row → event_id → /v1/events → nested market_id → /v1/markets — silently changed provider partway through.

Nothing in the response said so. The provider field was correct about what was returned; it just wasn't what you asked for.

What changed. Both endpoints now probe every candidate platform concurrently and answer only when exactly one of them holds the identifier. When two do, the request fails with 409 Conflict naming both instead of picking one:

{
  "error": "ambiguous market_id",
  "message": "market_id \"1607914\" resolves on polymarket and predict, which are different markets. Retry with ?platform= naming the one you want, or use the composite {platform}:{id} form.",
  "candidates": ["polymarket", "predict"],
  "status_code": 409
}

candidates is the actionable part: every entry is a legal platform value, so a client can retry automatically. The SDKs expose this as a typed ConflictError carrying an AmbiguousIdentifierError body.

GET /v1/events/{event_id} also now accepts the composite {provider}:{native_id} form that GET /v1/markets already returned in data[].id. Previously GET /v1/events/predict:1607914 was treated as an opaque ambiguous id and surfaced as 502; it now resolves.

Migration

This is breaking for one case only: a bare numeric id or kebab-case slug, sent with no ?platform=, that exists on both Polymarket and Predict. That request used to return a Polymarket 200 and now returns 409.

For Polymarket callers the change is small — on a uniform sample of 160 integer ids, 114 were real Polymarket markets and only 2 of those (2%) also existed on Predict. For Predict callers it converts a majority of silently-wrong responses into a loud, self-describing error. Nothing that returned the right market before returns an error now.

The fix is one parameter, and it is the same rule for every provider:

# before — inferred, and wrong 57% of the time for Predict ids
curl "$BASE/v1/markets/1607914"

# after — deterministic, one of:
curl "$BASE/v1/markets/1607914?platform=predict"
curl "$BASE/v1/markets/predict:1607914"

Every response that hands you an identifier also hands you its platform: GET /v1/markets returns the composite form directly in data[].id, and every row of GET /v1/matching-markets/sports carries a platform field that ?platform= accepts verbatim (case-insensitively, including ALPHA-ARCADE). So ?platform={row.platform} is a single safe rule across all six providers.

Naming the platform is also strictly more available than not naming it: the probe has to reach both candidates to prove there is no collision, so it fails if either is having an outage, while an explicit platform depends only on that one. Composite ids, explicit ?platform=, Kalshi tickers and SX Bet identifiers never probe and can never return 409.

On this page