Kalshi is hiring an Account Executive to sell event contract prices, order book data and historical datasets to hedge funds, banks and quant teams, and BMLL and LO:TECH now distribute the data to institutions. But docs.kalshi.com, where a quant researcher will look first, is written for API traders: about 290 pages on orders, rate limits and endpoints, and none on what data exists, its coverage by category, history depth, bulk delivery, licensing, the distributors or who to contact. The help center's API article still says the API is REST only with "a limited number of stats".
First action
List every dataset and field the AE will sell and where each is delivered.
How to measure it
Data evaluation requests from the docs
- Now
- –
- Target
- 20 a month
- By
- 90 days
Steps
Inventory datasets
Prices, order books, trades, candlesticks, settlements, weather index.
Account Executive / Account Manager, Data Sales 2 days
Map coverage
Categories and history depth for each dataset.
Data Scientist (Product) 1 week
Write the field dictionary
Fields, units, fixed-point prices, time zones.
Developer Relations Lead 1 week
Describe delivery
Direct API and WebSocket; distributor channels.
Account Executive / Account Manager, Data Sales 2 days
Legal review
Licensing, redistribution and use-case wording.
Legal 1 week
Publish a sample
One month of settled markets in CSV and Parquet.
Developer Relations Lead 3 days
Add the request form
Routed to Data Sales with firm type and use case.
Account Executive / Account Manager, Data Sales 1 day
Update the help article
Replace the REST-only text.
Developer Relations Lead 1 hour
Track
Visits, sample downloads and requests.
Account Executive / Account Manager, Data Sales weekly
Why it works
Add a "Market data" section to the docs: the datasets (prices, order books, trades, candlesticks, settlement and the weather index), coverage and history by category, a field dictionary, delivery options (API and WebSocket direct, Snowflake, SFTP and CSV through BMLL and LO:TECH), licensing and redistribution basics, a downloadable sample, and a request form routed to Data Sales. Update the help article to match. Have Legal and Compliance approve the licensing and use-case wording.
Institutional buyers qualify vendors on documentation before they take a call. A clear data page shortens evaluations, sends inbound requests to the new AE, and lets distributors and Kalshi tell the same story.
Ready to use
ChecklistMarket data docs page
[ ] Dataset list with coverage and history depth [ ] Field dictionary [ ] Direct delivery: REST, WebSocket, historical endpoints [ ] Distributor delivery: BMLL, LO:TECH [ ] Licensing and redistribution basics (Legal approved) [ ] Downloadable sample [ ] Request form routed to Data Sales [ ] Help article updated
Risks and how to handle them
Channel conflict with distributors
Show distributors as options and agree wording with them.
Claims about use cases
Keep descriptions factual and approved by Compliance.
Evidence
- HiringAccount Executive / Account Manager, Data Sales (posted September 29, 2026): sell "Kalshi's event contract prices, order book data, and historical datasets to hedge funds, asset managers, banks, proprietary trading firms, quantitative investment teams, and fintech companies"; run "data evaluations"; "explain data coverage, delivery methods, and integration requirements"; negotiate "API, data feed, and licensing agreements".Source
- News coverageBMLL (September 17, 2026) added Kalshi historical prediction market data, "normalising Kalshi's historical order book into the same unified schema as CME Event Contracts", delivered "through Snowflake, SFTP, or the BMLL Data Lab" for quantitative research teams and macro and systematic hedge funds backtesting around Fed decisions, CPI and GDP. In July 2026 LO:TECH became "a licensed distributor of Kalshi market data" (historical API, daily CSVs, WebSocket replay).Source
- Developer docsdocs.kalshi.com (index of about 290 pages, checked October 22, 2026) is written for API traders: quick starts for market data, authenticated requests, first orders and WebSockets; rate limits; historical endpoints (/historical/markets, /historical/trades, candlesticks) with cutoff timestamps. No page covers data licensing, redistribution, bulk or flat-file delivery, coverage by category, licensed distributors or a sales contact.Source
- Help centerHelp article "Kalshi API" (updated March 10, 2026): "Currently, the API is implemented as a REST API" and gives access to order books "and a limited number of stats about each of them", while the docs cover WebSockets, historical data, live game data and a weather index.Source
- Developer docsThe API serves a "Kalshi-computed city temperature index: the canonical minute-resolution series behind hourly temperature markets", with a published calibration timeline of station weights and offsets, plus play-by-play game statistics and CF Benchmarks data.Source