REST API / Matching / Match by URL

Matching Markets by URL

Find matching markets by providing a URL from any supported platform. The platform is auto-detected from the URL hostname.

Case Study

See how Elastics built their AI trading terminal on this endpoint→

Matches aren't always 100% accurate. Verify all data before executing a trade.

GET/v2/matching-markets/url

Query Parameters

urlstringRequired

Full URL from any supported platform (Polymarket, Kalshi, PredictIt, ProphetX, Opinion, Predict.fun).

Response Schema

successboolean

Whether matching events were found.

countinteger

Number of matching events returned.

eventsobject[]

Matched events with cross-platform market groups.

titlestring

Event name.

event_typestring

Category: economics, sports, election, etc.

event_datestring

Date of the event.

confidencestring

Match confidence: "high" or "medium".

groupsobject[]

Market groups within this event.

titlestring

Group title.

marketsobject[]

Matched markets: source, source_url, id.

Error Responses

All errors return the same envelope. The code field is stable and programmatically branchable; error and message are human-readable. errors[] is present only on validation failures with field-level detail. See the full error code reference →

successboolean

Always `false` on error responses.

errorstring

Short, human-readable title (e.g. 'Invalid API Key.').

messagestring

Human-readable explanation for the error. Safe to surface in UIs.

codestring

Stable, hierarchical machine-readable code (e.g. 'validation.invalid_enum'). Use for programmatic handling.

doc_urlstring

Link to this code's entry in the Error Reference.

errorsobject[]

Optional. Present only on validation failures with field-level detail.

fieldstring

Name of the offending parameter.

codestring

Field-level machine code.

messagestring

Human-readable explanation.

Authentication

API Key

To secure your requests, we strongly recommend passing your API key via the X-API-Key header. This prevents sensitive keys from being exposed in access logs or browser history.

Request HeaderX-API-Key: pmx_test_5e8f...

Rate Limits

API rate limits are enforced based on the tier associated with your API key. Limits are tracked on two dimensions: requests per second and requests per month. Each completed request counts toward the global monthly quota. Separate endpoint-group monthly limits (matched markets, arbitrage, EV) only advance when the response body has success: true.

Usage is returned on responses via headers such as:

Response Headers (global)X-RateLimit-Limit-Second: 10X-RateLimit-Remaining-Second: 9X-RateLimit-Limit-Month: 1000X-RateLimit-Remaining-Month: 842Example (endpoint-group, when applicable)X-RateLimit-Limit-Arb-Month: 500X-RateLimit-Remaining-Arb-Month: 412

If you exceed a rate limit, the API returns a 429 status with a Retry-After header indicating when you can resume.

Request

Live API Key

Demo Mode

Verified

Market URL

Platform URLRequired

Response

—

Click EXECUTE to send a request →