Odds API Racing events API

Racing event discovery and live racing event updates.

Operations 4

GET /racing/events Racing events: Search #
GET /racing/events/stream Racing events: Stream (SSE) #
GET /racing/events/ws Racing events: Stream (WebSocket) #
GET /racing/events/{event_id} Racing events: Event details #

Documentation

Specifications

Other Resources

🔗
PostmanCollection
https://github.com/odds-api/odds-api/blob/main/postman/odds-api.postman_collection.json
🔗
LLMsTxt
https://odds-api.net/llms.txt
🔗
ToolCrosswalk
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/mcp/odds-api-tool-crosswalk.yml
🔗
SDKs
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/packages/odds-api-packages.yml
🔗
Packages
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/packages/odds-api-packages.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/errors/odds-api-problem-types.yml
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/conventions/odds-api-conventions.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/data-model/odds-api-data-model.yml
🔗
Sandbox
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/sandbox/odds-api-sandbox.yml
🔗
Plans
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/plans/odds-api-plans-pricing.yml
🔗
Conformance
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/conformance/odds-api-conformance.yml
🔗
Lifecycle
https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/lifecycle/odds-api-lifecycle.yml
🔗
StatusPage
https://odds-api.net/sla-status-support
🔗
Pricing
https://odds-api.net/pricing
🔗
SignUp
https://odds-api.net/signup

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/odds-api-racing-events-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

odds-api-racing-events-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Odds Racing events API
  description: 'The Odds API V1 provides sports and racing events, bookmaker odds, exchange and prediction-market order books,

    live price updates, betting opportunity snapshots, and result lookups for production integrations.'
  version: 1.0.0
  license:
    name: Proprietary
    url: https://odds-api.net
  x-workflow-examples:
  - name: positive_ev_request
    summary: Find positive EV bets for a league.
    steps:
    - GET /v1/events?sport=rugby-league&league=NRL
    - GET /v1/bets/snapshot?strategies=pos_ev
    - Use response timestamps and stake/risk controls before showing user-facing picks.
  - name: arbitrage_request
    summary: Find arbitrage opportunities across allowed bookmakers.
    steps:
    - GET /v1/bookmakers
    - GET /v1/bets/snapshot?strategies=arbitrage
    - Show execution-risk caveats; never present arbitrage as guaranteed after limits, voids, or delays.
  - name: odds_history_request
    summary: Get line movement for a market.
    steps:
    - GET /v1/events/{event_id}/odds/snapshot
    - Pick a selection_key from an odds line.
    - GET /v1/events/{event_id}/odds/history?selection_key=...
  - name: prediction_market_orderbook_request
    summary: Read and follow a curated prediction-market order book.
    steps:
    - GET /v1/events?sport=basketball&league=NBA
    - GET /v1/events/{event_id}/prediction-markets/orderbook/snapshot?providers=polymarket,kalshi&depth=3
    - Connect to the matching /stream or /ws route with since=<snapshot resume>.
  x-responsible-gambling: Do not present betting outcomes as risk-free. Always mention execution risk, stale prices, bookmaker limits, voids, delays, and jurisdictional availability in user-facing products.
  x-production-integration:
    recommended_flow:
    - Authenticate backend requests with X-API-Key.
    - Discover sports, leagues, and bookmakers before storing local filters.
    - Page sports or racing events with limit and cursor.
    - Fetch odds snapshots for initial state. Explicit bookmaker filters are complete in one response; otherwise follow bookmaker-complete pages until complete=true. Persist as_of_ts_ms, ttl_seconds, and resume.
    - Use SSE or WebSocket streams for realtime updates and reconnect with since=<last_resume>.
    - Use history endpoints for line movement and results endpoints after events finish.
    recommended_polling_intervals:
      catalog_metadata: 6-24h
      sports_events: 5-15m, or 1-5m for active leagues and near-start windows
      racing_events: 1-5m with narrow time windows
      odds_snapshots_without_streams: 60-120s, or 15-30s for priority events with strict quota controls
      betting_opportunity_snapshots: 30-120s depending on alert urgency
      results_after_start: 1-5m until settled, then back off
    stream_reconnects:
    - Snapshot first, then connect to /stream or /ws with matching filters.
    - Apply delta messages idempotently and persist the newest resume token.
    - Use heartbeat messages as liveness checks.
    - Reconnect with jittered exponential backoff and since=<last_resume>.
    - Reload the snapshot when a resync message indicates the resume token is unavailable.
    rate_limit_backoff:
    - Honor Retry-After on 429 when present.
    - Otherwise start around 2 seconds and double up to about 60 seconds with jitter.
    - Use X-RateLimit-* response headers when present to tune callers.
    - Use /usage to detect monthly API-credit quota exhaustion and stop retry loops.
    cache_strategy:
    - Cache by endpoint path, event ID, normalized filters, page cursor, and product context.
    - Respect ttl_seconds when present and always surface as_of_ts_ms.
    - Use streams to update hot caches and reload snapshots after resync or parse failure.
    - Prefer stale-while-revalidate displays with a visible timestamp.
    failure_modes:
    - 400 invalid request shape, cursor, timestamp, or filter.
    - 401 missing or invalid API key.
    - 403 key lacks plan, product, bookmaker, stream, racing, or strategy access.
    - 404 event, race, result, or selection is unavailable.
    - 429 rate limit or monthly quota exhaustion.
    - 5xx transient service failure; retry with backoff and keep last good cached data marked stale.
    - Stream close or resync; reconnect with since or reload the snapshot.
servers:
- url: https://api.odds-api.net/v1
  description: Production V1 base URL. Set ODDS_API_BASE_URL to override it in SDKs and examples.
security:
- ApiKeyAuth: []
tags:


# --- truncated at 32 KB (36 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/odds-api/refs/heads/main/openapi/odds-api-racing-events-api-openapi.yml