Prediction-market category discovery
Use DraftKings Predictions endpoints to turn prediction-market category discovery into repeatable API requests with documented inputs and JSON responses.
Read the public navigation and reference material from DraftKings Predictions without confusing it for a market feed. The endpoints return category links, settlement-source references, and a region/status map; they do not return quotes, trades, balances, or trade-slip state.
Collect DraftKings Predictions' public category navigation, rule sources, settlement links, and availability map as JSON.
Endpoint families
1
Documented params
3
Examples
3
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
3
Schema refs
3
{
"platform": "DraftKings Predictions",
"endpoint": "draftkings-predictions-categories",
"method": "GET",
"path": "/draftkings/predictions/categories",
"auth": "apiKey"
}Use cases
Collect DraftKings Predictions' public category navigation, rule sources, settlement links, and availability map as JSON.
Use DraftKings Predictions endpoints to turn prediction-market category discovery into repeatable API requests with documented inputs and JSON responses.
Use DraftKings Predictions endpoints to turn settlement-source reference lookup into repeatable API requests with documented inputs and JSON responses.
Use DraftKings Predictions endpoints to turn public availability-map analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live DraftKings Predictions endpoint catalog — 3 endpoints, 3 documented request parameters, and 3 published response schemas — the same catalog Docs and Playground run against.
3 documented DraftKings Predictions endpoints, all in the Predictions family.
3 request parameters are documented across those DraftKings Predictions endpoints, 3 of them required — the full input contract is public before you write any integration code.
3 of the 3 DraftKings Predictions endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
DraftKings Predictions endpoints document their error responses (429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the DraftKings Predictions endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/draftkings/predictions/categories
Endpoint catalog
/draftkings/predictions/categoriesReturns the public category and league navigation from the DraftKings Predictions homepage. It excludes market quotes, trade-slip selections, accounts, balances, promotions, and location data. Market availability varies by location and time; this endpoint is a navigation directory, not trading advice.
Response notes
and leagues. `fetched_at` is when this API retrieved the page.
Sampled 25 Oct 2026: 16 items, 3 fields filled in every item. name: “Football” and 15 other values; leagues: median 3 entries.
MCP tool draftkings_predictions_categories
/draftkings/predictions/rulesLists public rulebook and settlement-source links from the DraftKings Predictions Rules and Settlements page. It does not fetch market data, quotes, trades, user state, or location context.
MCP tool draftkings_predictions_rules
/draftkings/predictions/availabilityReturns the 52 region/status mappings shown on DraftKings Predictions' public availability map. Allowed `status` values: `all_markets_available`, `financial_markets_only`, `sports_markets_unavailable`, `no_markets_available`. This source map is not a complete legal eligibility matrix and does not separately classify all territories or tribal land. It does not read caller location or trading/account state.
MCP tool draftkings_predictions_availability
Related APIs
Prediction Markets
Collect Polymarket event and market detail, token prices, order books, midpoints, spreads, price history, tags, sports, leaderboards, and trade activity as normalized JSON for dashboards, research, and agent-native workflows. Not investment advice or real-time trading data.
Prediction Markets
Collect Kalshi events, markets, series, recent trades, order books, exchange schedule, and historical market candlesticks as normalized JSON for dashboards and research. Not investment advice or real-time trading data.
Prediction Markets
Collect Metaculus questions, community forecasts and forecast history, question metadata, options, and comment feeds as normalized JSON for research and tracking. Not investment, forecasting, or decision advice.
How to scrape DraftKings Predictions
The DraftKings Predictions homepage observed on 2026-10-25 grouped its navigation into 16 categories spanning sports and topics such as economics, culture, and climate. A live rules response on 2026-10-24 returned 5 rule-source links and 8 settlement links across 4 categories; those references are informational, and DraftKings warns its site data is unofficial and not for trading reliance.
Call /draftkings/predictions/categories for the public category and league navigation. It is a current snapshot: categories and their ordering can change, and the response does not include prices, market availability, or account state.
Use /draftkings/predictions/rules to retrieve the public rulebook and settlement-source links. The live response observed on 2026-10-24 contained 5 rule-source links plus 8 settlement links grouped into 4 categories.
Call /draftkings/predictions/availability for the region/status mappings shown on the product page. The map does not read the caller's location and is not a complete legal-eligibility matrix.
FAQ
No. The public endpoints cover navigation, rules and settlement links, and the displayed availability map. They do not expose quotes, trades, balances, or a trade slip.
No. It reports the mappings shown on the public page, not the caller's location or account state, and it is not a complete legal-eligibility matrix.
DraftKings states that market availability varies and that site information is unofficial and should not be relied on for trading. Crawlora's endpoints here are reference-data snapshots, not a trading feed.