REST API / Signals / Arbitrage

Arbitrage

Cross-platform arbitrage opportunities. Buying YES on one platform and NO on another guarantees a risk-free profit after fees. API response will include a 15-second signal delay.

Requires Dev or Pro tier. This endpoint is not available on the Free tier.Upgrade ↗

GET/v2/arb

Query Parameters

min_roifloat

Minimum ROI percentage to include. Default: 0 (no minimum).

platformsstring

Filter to specific platform pair, e.g. polymarket,kalshi.

limitinteger

Default: 20, max: 100.

Response Schema

as_ofstring

Server timestamp of the response (ISO 8601).

delay_secondsinteger

Signal delay in seconds applied to the response.

countinteger

Number of opportunities returned.

opportunitiesobject[]

Current arbitrage opportunities.

group_idinteger

Match group ID.

group_titlestring

Human-readable group title.

event_datestring

Event date.

event_typestring

Event category.

roi_pctnumber

Return on investment percentage.

total_costnumber

Total cost to execute (YES price + NO price).

detected_atstring

When this opportunity was detected (ISO 8601).

legsobject[]

The two legs of the arbitrage trade.

sidestring

"yes" or "no".

platformstring

Platform for this leg.

market_idstring

Market ID on the platform.

source_urlstring

Direct link to the market.

pricenumber

Price for this leg.

liquidity_usdnumber

Available liquidity in USD.

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

Filters

Min ROI %

Platforms

Limit

Response

—

Click EXECUTE to send a request →