odds-api.io valid

Odds API (odds-api.io)

Real-time sports betting odds API with data from 415+ bookmakers across 34 sports via a single REST API.

For agents: REST API delivering real-time sports betting odds from 415+ bookmakers across 34 sports, including esports, plus bet settlement endpoints and docs.

sports betting oddsodds apibookmaker dataesports oddsbet settlementrest api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T21:33:46.821Z. Cached copy · Source on odds-api.io

# Odds API (odds-api.io)

> Real-time sports betting odds API with data from 415+ bookmakers across 34 sports via a single REST API.

## What is Odds API?

Odds API is a B2B REST API that provides real-time and historical sports betting odds from 415+ bookmakers across 34 sports. It serves developers building odds comparison sites, arbitrage tools, value bet finders, trading bots, and sports analytics platforms.

## Key Facts

- 415+ bookmakers (Bet365, DraftKings, FanDuel, Betfair, SBOBET, BetMGM, Unibet, SingBet, and more)
- 34 sports (Football, Basketball, Tennis, NFL, NBA, NHL, MLB, Esports, Cricket, and more)
- 12,000+ leagues and competitions worldwide
- Pre-match and live/in-play odds
- 500+ market types (ML, Asian Handicap, Totals, Player Props, Correct Score, and more)
- Value bet detection and arbitrage opportunity detection
- Historical odds data and odds movement tracking
- WebSocket real-time streaming
- Direct bet links to bookmaker sites
- 99.9% uptime target
- <150ms average response time
- 20,000+ developers worldwide
- Live scores and match status streaming over WebSocket (~1 second updates)

## API Endpoints

Base URL: https://api.odds-api.io/v3

### No Authentication Required
- GET /v3/sports: List available sports
- GET /v3/bookmakers: List available bookmakers

### Authenticated (apiKey required)
- GET /v3/leagues: List leagues for a sport
- GET /v3/events: List events (filter by sport, league, status, bookmaker, date range)
- GET /v3/events/live: Get currently live events (includes optional clock object: minute, playedSeconds, period, running, statusDetail, serve, injuryTime)
- GET /v3/events/search: Search events by text query
- GET /v3/events/{id}: Get event by ID
- GET /v3/odds: Get odds for a specific event from selected bookmakers
- GET /v3/odds/multi: Get odds for multiple events in one call (up to 10, counts as 1 request)
- GET /v3/odds/updated: Get odds updated since a timestamp (for incremental polling)
- GET /v3/odds/movements: Get historical odds movements for a market
- GET /v3/markets: List available betting markets
- GET /v3/historical/events: List past events for a sport/league/season
- GET /v3/historical/events/search: Search past events by text query
- GET /v3/historical/odds: Get historical odds for a past event
- GET /v3/historical/closing-lines: Get closing lines for a past event
- GET /v3/value-bets: Prices above a fair-odds estimate (expected value calculation)
- GET /v3/arbitrage-bets: Find arbitrage opportunities across bookmakers
- GET /v3/dropping-odds: Get dropping odds from sharp bookmakers (paid plans only)
- GET /v3/settlements: Result, status and final flag for up to 50 events (paid plans)
- POST /v3/settlements/grade: Grade up to 50 bets as won, lost, void, half_won or half_lost (paid plans)
- GET /v3/participants: Get teams/participants for a sport
- GET /v3/participants/{id}/logo: Get participant crest as PNG (hotlinkable, served from our domain)
- GET /v3/bookmakers/selected: Get user's se
…

Related sites

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=odds-api.io · GET /v1/domain/odds-api.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for odds-api.io:
1. POST https://agentwebmap.com/v1/sites/odds-api.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://odds-api.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/odds-api.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/odds-api.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.