Events
List all tracked events with their matched market groups. Events are the real-world occurrences that markets are tied to. Each event can have multiple matched market groups across platforms.
/v2/eventsQuery Parameters
Filter: sports, election, economics, or all. Default: all.
Filter by status: active (event date today or future), completed (past), or all. Default: active.
For sports events: nfl, nba, mlb, nhl, cfb, epl, etc. Comma-separated.
Filter by event date (YYYY-MM-DD).
Search event name.
Default: 20, max: 100.
Pagination cursor from previous response.
Response Schema
List of events matching the filters.
Internal event ID.
Event name (e.g. "NBA: Lakers vs Celtics").
Category: sports, election, economics.
Date of the event (YYYY-MM-DD).
Event status: active (event date is today or future) or completed (event date has passed).
Matched market groups for this event.
Internal match group ID.
Group title (e.g. "lakers win").
Number of platforms with markets in this group.
List of platform names (e.g. ["polymarket", "kalshi"]).
Opaque cursor for the next page. Null if no more results.
Total number of events matching the filters.
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 →
Always `false` on error responses.
Short, human-readable title (e.g. 'Invalid API Key.').
Human-readable explanation for the error. Safe to surface in UIs.
Stable, hierarchical machine-readable code (e.g. 'validation.invalid_enum'). Use for programmatic handling.
Link to this code's entry in the Error Reference.
Optional. Present only on validation failures with field-level detail.
Name of the offending parameter.
Field-level machine code.
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.
X-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:
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: 412If 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
Filters
Response
—Click EXECUTE to send a request →