GET/api/v1/events
Search events
Every event whose words hold every word of q, on every venue, newest close first. It is the list behind search's more_events.
Needs an API key from your code (a free account has one). An event's words are its id, title, subtitle, series id and name, and category: temperature finds the NYC high-temperature events through their series name. Whole words, any case; single letters and words like the are skipped, and a q with nothing else is 400. One event with its markets is Get event.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
q | string | required | The words (lakers celtics) |
venue | string | — | kalshi, polymarket, limitless or chainlink |
status | string | — | live, closed, settled, or a data status as on Search catalog |
category | string | — | A category as List categories names it; an unknown one is 400 |
from_ts / to_ts | number | — | Unix seconds: events open at any time in this window |
limit | int | 50 | Events a page, 1–200 |
cursor | string | — | The response's next_cursor, for the next page (offset works too, slower on deep pages) |
curl "https://kalshieye.com/api/v1/events?q=lakers+celtics&limit=2" \
-H "Authorization: Bearer $KALSHIEYE_API_KEY"The response has events (each as search shows it, with its venue), count on this page, total, total_exact, next_cursor and next_offset. total counts exactly up to 10,000; past that it is 10,000 and total_exact is false (show "10,000+"), and the pages still reach every event. Pass next_cursor as cursor until it is null; see Paging.