Polymarket events

GET https://api.api.sh/polymarket/v1/events
1 credit / call finance & crypto try it in the playground →

Prediction-market events on Polymarket (an event groups one or more markets): title, description, image, status, volume (total, 24 h, 1 w, 1 m, 1 y), liquidity, open interest, comment count, dates, tags, series and each market with its outcomes and prices. Filter by status, tag, series, featured, volume and liquidity floors and start/end date windows; sort by volume, liquidity, dates or competitiveness. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
status open | closed | all open (default), closed or all. Example: open
tag string Tag slug, e.g. politics, crypto, sports, elections, economy, tech. Example: politics
series string Series slug for recurring events.
featured boolean true for featured events only.
sort volume_24h | volume | liquidity | start_date | end_date | created_at | competitive | comments volume_24h (default), volume, liquidity, start_date, end_date, created_at, competitive or comments.
sort_dir desc | asc desc (default) or asc.
min_volume number Minimum total volume (USD).
max_volume number Maximum total volume (USD).
min_liquidity number Minimum liquidity (USD).
max_liquidity number Maximum liquidity (USD).
start_after string Events starting on/after this date (ISO).
start_before string Events starting on/before this date (ISO).
end_after string Events ending on/after this date (ISO).
end_before string Events ending on/before this date (ISO).
markets boolean false leaves out each event's markets (smaller answer).
page integer Page number (default 1).
limit integer Events per page, 1-100 (default 50).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/polymarket/v1/events?status=open" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.