SDK drift: Router.fetchEventMatches missing `url` parameter in TypeScript

[realfishsam]

Drift

Router.fetchEventMatches in the TypeScript SDK does not accept a url parameter. The Python SDK accepts url: Optional[str] = None, which allows callers to resolve an event by its URL. The parameter exists on fetchMarketMatches in both SDKs.

TypeScript SDK

File: sdks/typescript/pmxt/router.ts lines 302–320

The method overloads accept event?, eventId?, slug?, relation?, minConfidence?, limit?, and includePrices? — but no url parameter. By contrast, the sibling method fetchMarketMatches (lines 183–215) does accept url?.

Python SDK

File: sdks/python/pmxt/router.py lines 239–307

def fetch_event_matches(
    self,
    event: Optional[UnifiedEvent] = None,
    event_id: Optional[str] = None,
    slug: Optional[str] = None,
    url: Optional[str] = None,   # <-- present in Python, absent in TypeScript
    relation: Optional[str] = None,
    min_confidence: Optional[float] = None,
    limit: Optional[int] = None,
    include_prices: Optional[bool] = None,
) -> List[EventMatchResult]:

Expected

Both SDKs should accept a url parameter on fetchEventMatches / fetch_event_matches, consistent with how fetchMarketMatches / fetch_market_matches works in both SDKs.

Impact

TypeScript callers cannot look up event matches by URL. They must use eventId or slug instead, diverging from Python behaviour and blocking URL-first workflows.

---

Found by automated SDK cross-language drift audit