Skip to main content
GET
Faster with an API key — With a PMXT API key this endpoint is served from an indexed catalog (~10 ms) instead of proxying to the venue (~500 ms). No code changes required — same request, same response, just faster. Learn more.

Use cases

Look up by slug

Slugs are stable, human-readable identifiers that make your code self-documenting and resilient to ID changes. Use them whenever possible.

Look up by market ID

When you already have a venue-native market ID (e.g. from a trade confirmation or webhook), pass it directly:

Read outcomes and prices

Every market carries an outcomes array and, for binary markets, yes / no convenience accessors with live prices:

Path Parameters

exchange
enum<string>
required

The prediction market exchange to target.

Available options:
polymarket,
kalshi,
kalshi-demo,
limitless,
probable,
baozi,
myriad,
opinion,
metaculus,
smarkets,
polymarket_us,
gemini-titan,
hyperliquid,
suibets,
rain,
hunch,
router

Query Parameters

limit
number

Maximum number of results to return

offset
number

Pagination offset — number of results to skip

sort
enum<string>

Sort order for results

Available options:
volume,
liquidity,
newest
status
enum<string>

Filter by market status (default: 'active', 'inactive' and 'closed' are interchangeable)

Available options:
active,
inactive,
closed,
all
searchIn
enum<string>

Where to search (default: 'title')

Available options:
title,
description,
both
query
string

For keyword search

slug
string

For slug/ticker lookup

marketId
string

Direct lookup by market ID

outcomeId
string

Reverse lookup -- find market containing this outcome

eventId
string

Find markets belonging to an event

page
number

For pagination (used by Limitless)

similarityThreshold
number

For semantic search (used by Limitless)

sourceExchange
string

Filter by source venue (e.g. 'polymarket', 'kalshi', 'myriad'). exchange is an alias.

exchange
string

Alias for sourceExchange.

Response

200 - application/json

Fetch Market response

success
boolean
Example:

true

error
object

Structured error envelope returned inside BaseResponse.error and ErrorResponse.error. Hosted-mode endpoints populate code, retryable, and optionally exchange / detail; legacy local-mode endpoints may still return only message.

data
object