Skip to content
OddsLinkOddsLink

Overview

Live odds and prices from every book we cover, in one JSON API.

OddsLink API 1.0.0

Section titled “OddsLink API 1.0.0”

Response format

OddsLink provides prices in a clear, consistent format. A price older than its book’s normal update rhythm is removed rather than shown as stale. No maximum age is promised.

  • Send your API key in the X-API-Key request header.
  • last_update is the time a book last confirmed a price. It can be null when that time is unavailable, and it is never an estimate.
  • size is included when a book publishes a posted limit, exchange depth, or contract count.
  • unmatched_bookmakers names a book when a price cannot be matched safely to a fixture.
  • Fixture ids are readable but should be treated as opaque strings. The date in an id can remain from an earlier scheduled kickoff. Read commence_time for the current scheduled kickoff.

What counts as a request

Price and history calls count against your monthly allowance. Listing sports and fixtures is free on every plan. Each operation states whether it counts against the allowance.

Information

  • License: Proprietary
  • OpenAPI version: 3.1.0

Operations

Section titled “ Operations ”
POST
/v1/contact
GET
/v1/tryit/run
GET
/v1/sports
GET
/v1/bookmakers
GET
/v1/pickem/payouts
GET
/v1/markets
GET
/v1/sports/{sport}/events
GET
/v1/sports/{sport}/events/live
GET
/v1/sports/{sport}/odds
GET
/v1/sports/{sport}/odds/live
GET
/v1/sports/{sport}/events/{id}/odds
GET
/v1/sports/{sport}/props
GET
/v1/sports/{sport}/props/live
GET
/v1/sports/{sport}/events/{id}/props
GET
/v1/historical/sports/{sport}/events
GET
/v1/historical/sports/{sport}/events/{id}/odds
GET
/v1/historical/sports/{sport}/events/{id}/openers
GET
/v1/historical/sports/{sport}/events/{id}/closing
GET
/v1/historical/sports/{sport}/events/{id}/props
GET
/v1/historical/sports/{sport}/events/{id}/props/movement
GET
/v1/historical/sports/{sport}/events/{id}/props/openers
GET
/v1/historical/sports/{sport}/events/{id}/props/closing
GET
/v1/account/usage
GET
/v1/account/usage/session
GET
/v1/account/usage/history/session
GET
/v1/account/plan
GET
/v1/account/keys
POST
/v1/account/keys
DELETE
/v1/account/keys/{keyId}
POST
/v1/billing/checkout
POST
/v1/billing/card
GET
/v1/billing/subscription
POST
/v1/billing/change
POST
/v1/billing/cancel
POST
/v1/billing/resume
GET
/v1/public/board/sports
GET
/v1/public/board/{sport}
GET
/v1/public/featured

Authentication

Section titled “ Authentication ”

ApiKeyAuth

Section titled “ApiKeyAuth”

Every operation except /v1/account/keys accepts this. There is no ?apiKey= query fallback.

Security scheme type: apiKey

Header parameter name: X-API-Key

BearerAuth

Section titled “BearerAuth”

A signed-in website session’s access token. Required by /v1/account/keys. An X-API-Key is refused there: only a signed-in customer creates or revokes keys.

Security scheme type: http