MARKETS & FINANCE
Kalshi Sports Markets
Track live Kalshi sports markets in one run: game lines, spreads, totals and prices, with the event, league, market type, line, yes/no prices, volume and liquidity per record.
About this data
Track live Kalshi sports markets in one run: game lines, spreads, totals and prices, with the event, league, market type, line, yes/no prices, volume and liquidity per record. Source identifiers are preserved for cross-book comparison, and every run returns a fresh full-board snapshot.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/kalshi/sports
Current open contracts from one sports series: KXNBAGAME (default), KXNFLGAME, KXNHLGAME, KXMLBGAME, KXNCAAFGAME, KXNCAAMBGAME, KXEPLGAME, KXNBASPREAD or KXNBATOTAL.
One representative Yes/No contract per event, soonest upcoming first, then started games, then unknown starts, among the first 200 open events.
Within each event, prefer two-sided quotes nearest 50%, then the narrowest spread, then ticker.
Includes game title, participants, published milestone kickoff and league, native market family, primary rules, volume and source link.
Bid/ask values are displayed sell/buy quotes in dollars per $1 contract, excluding fees and depth; lastPrice is the last trade (zero can mean no trades).
Probabilities use a valid two-sided midpoint, otherwise an interior last trade with positive volume, otherwise null; decimal odds are indicative and rounded to two decimals.
No complements the stated Yes proposition; it does not necessarily mean the opponent wins.
Game legs retain canonical unsupported status for cross-book comparison; spread/total lines are canonical only when verified.
Liquidity appears only when published.
Input
Send a JSON body to POST https://api.ssh.autos/v1/kalshi/sports.
| Field | Type | Required | Notes |
|---|---|---|---|
seriesTickers | array of strings | optional | exactly 1 item; default ["KXNBAGAME"] |
maxResults | integer | optional | 1–5; default 3 |
Returned fields
The answer is JSON: records, a list of up to 5, and summary, the run status and counts. Each record has these 45 fields; a field the source does not publish comes back null.
45 fields per record
| Field | Type | Notes |
|---|---|---|
recordKey | string | — |
source | string | always kalshi |
sourceUrl | string | — |
ticker | string | — |
status | string | — |
eventTicker | string | — |
eventTitle | string | — |
eventSubTitle | string | — |
participants | array of strings | Both participants split from a verified fixture title; listing order, not home/away. |
startTime | string | Kickoff from an explicitly linked milestone; occurrenceTime is not kickoff. |
startTimeSource | string | — |
sport | string | Sport from the linked milestone type. |
yesProbability | number | — |
noProbability | number | — |
probabilitySource | string | one of bid_ask_midpoint, last_trade |
seriesTicker | string | — |
seriesTitle | string | — |
frequency | string | — |
leagueLabel | string | — |
competitionScope | string | — |
mutuallyExclusive | boolean | — |
marketType | string | one of moneyline, moneyline_3way, spreads, totals, props, unsupported, unknown |
marketTypeKind | string | — |
strikeType | string | — |
floorStrike | number | — |
capStrike | number | — |
floorStrikeRaw | string | — |
capStrikeRaw | string | — |
yesSubTitle | string | — |
noSubTitle | string | — |
occurrenceTime | string | — |
openTime | string | — |
closeTime | string | — |
lastPrice | number | — |
yesBid | number | — |
yesAsk | number | — |
noBid | number | — |
noAsk | number | — |
volume | number | — |
liquidity | number | — |
outcomeYes | string | — |
outcomeNo | string | — |
canonical | object | — |
collectedAt | string | — |
rulesPrimary | string | — |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/kalshi/sports -m POST -b '{"seriesTickers": ["KXNBAGAME"], "maxResults": 3}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- No open matches returns records: []
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- source failures and timeouts are not charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Kalshi Sports Markets. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt