TheRundown API

TheRundown API

TheRundown is the leading platform for real-time odds, scores, stats, and unrivaled insights into the sports betting marketplace.
Free Plan $0.00 Monthly Subscribe
750 Requests / Monthly
Free for Lifetime
No Credit Card Required
MOST POPULAR
Starter Plan $49.99 Monthly Subscribe
3,000 Requests / Monthly
Standard Support
Instant Line Updates
Live Scores
Line Take-down Notices
Teams and Schedules
Pro Plan $199.99 Monthly Subscribe
30,000 Requests / Monthly
Standard Support
Instant Line Updates
Live Scores
Line Take-down Notices
Teams and Schedules
Custom Plan Volume Monthly Contact Us
Any requests volume you need
Instant Line Updates
Live Scores
Line Take-down Notices
Teams and Schedules
NFL, NBA, WNBA, MLB, NHL, NCAA Football, NCAA Basketball, MLS, EPL, Bundesliga, Ligue 1, La Liga, Serie A, UEFA Champions with more sports soon. Live In-play odds are available for 5Dimes, Pinnacle, Matchbook, Bovada, Bodog, Draftkings, Pointsbet, Unibet, and BetMGM. Over a dozen sportsbooks currently integrated: 5Dimes, Pinnacle, Matchbook, Betcris, Lowvig, YouWager, Justbet, Tigergaming, Betonline, Bookmaker, Sportsbetting, Intertops & more coming soon. Moneyline, Spread, & Total for full-games, 1st half, 2nd half, 1st Quarter/Period, 2nd Quarter/Period, 3rd Quarter/Period, and 4th Quarter/Period with more markets coming soon.

TheRundown API Reference

This API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Just Getting Started?

Check out our development quickstart guide.

Authentication

TheRundown API uses API keys to authenticate requests. You can view and manage your API keys in the Accounts page.

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.

All requests made to the API must hold a custom HTTP header named "apikey". Implementation differs with each programming language. Below are some samples.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Endpoints

Gets the available sportsbooks.

Parameters
No parameters.
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get events that have changed.

Parameters

last_id (required)

The delta_last_id included in any of the events or delta endpoints.

Location: Query, Data Type: string

include (optional)

Can be one or many of scores or all_periods.

Location: Query, Data Type: string

sport_id (optional)

May be used to filter the changed events by sport.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get odds, scores, and other information for a single event.

Parameters

event-id (required)

the event_id of the event.

Location: Path, Data Type: string

include (optional)

Can be one or many of scores or all_periods.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get historical information for a single lines moneyline.

Parameters

line-id (required)

The line Id.

Location: Path, Data Type: string

include (optional)

Can be one or many of scores or all_periods.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get historical information for a single lines spread.

Parameters

line-id (required)

The line Id.

Location: Path, Data Type: string

include (optional)

Can be one or many of scores or all_periods.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get historical information for a single lines total or over/under market.

Parameters

line-id (required)

The line Id.

Location: Path, Data Type: string

include (optional)

Can be one or many of scores or all_periods.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get available sports and their identifiers.

Parameters
No parameters.
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get Closing lines by sport and date.

Parameters

date (required)

Event date.

Location: Path, Data Type: string

sport-id (required)

Sport Id.

Location: Path, Data Type: string

include (optional)

Can be one or many of scores or all_periods.

Location: Query, Data Type: string

offset (optional)

Offset in minutes from UTC.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get the dates that contain odds for events that are on or after the current date and have not yet started.

Parameters

sport-id (required)

The sport Id.

Location: Path, Data Type: string

format (optional)

epoch to get unix epoch instead of ISO8601 format.

Location: Path, Data Type: string

offset (optional)

offset in minutes from UTC.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get events by sport and date.

Parameters

date (required)

Event date.

Location: Path, Data Type: string

sport-id (required)

Sport Id.

Location: Path, Data Type: string

include (optional)

Can be one or many of scores or all_periods.

Location: Query, Data Type: string

offset (optional)

Offset in minutes from UTC.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Get opening lines by sport and date.

Parameters

date (required)

Event date.

Location: Path, Data Type: string

sport-id (required)

Sport Id.

Location: Path, Data Type: string

include (optional)

Can be one or many of scores or all_periods.

Location: Query, Data Type: string

offset (optional)

Offset in minutes from UTC.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Gets the schedule for a sport.

Parameters

sport-id (required)

The sport Id.

Location: Path, Data Type: string

from (optional)

Used to get the date at which the games are returned.

Location: Query, Data Type: string

limit (optional)

Used to set the number of events returned in the response.

Location: Query, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Gets the teams for a sport.

Parameters

sport-id (required)

The sport Id.

Location: Path, Data Type: string

** A word enclosed with curly brackets "{ }" in the code means that it is a parameter and it should be replaced with your own values when executing. (also overwriting the curly brackets).
Returns

Below is a sample response from the endpoint


If you wish to play around interactively with real values and run code, see...

Rate Limiting

Each subscription has its own rate limit. When you become a member, you start by choosing a rate limit that suits your usage needs. Do not worry; You can upgrade or downgrade your plan at any time. For this reason, instead of starting with a larger plan that you do not need, we can offer you to upgrade your plan after you start with "free" or "gold plan" options and start using the API.

When you reach a rate limit (both daily and monthly), the service will stop responding and returning the HTTP 429 response status code (Too many requests) for each request with the following JSON string body text.

{
"message":"You have exceeded your daily\/monthly API rate limit. Please review and upgrade your subscription plan at https:\/\/apilayer.com\/subscriptions to continue."
}

A reminder email will be sent to you when your API usage reaches both 80% and 90%, so that you can take immediate actions such as upgrading your plan in order to prevent your application using the API from being interrupted.

You can also programmatically check your rate limit yourself. As a result of each request made to the APILayer, the following 4 fields provide you with all the necessary information within the HTTP Headers.

x-ratelimit-limit-month: Request limit per month
x-ratelimit-remaining-month: Request limit remaining this month
x-ratelimit-limit-day: Request limit per day
x-ratelimit-remaining-day: Request limit remaining today

You can contact our support unit if you need any assistance with your application regarding to handle the returned result by looking at the header information.

Error Codes

APILayer uses standard HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate a clientside error, which means that failed given the information provided (e.g., a missing parameter, unauthorized access etc.). Codes in the 5xx range indicate an error with APILayer's servers (normally this should'nt happen at all).

If the response code is not 200, it means the operation failed somehow and you may need to take an action accordingly. You can check the response (which will be in JSON format) for a field called 'message' that briefly explains the error reported.

Status Code Explanation
400 - Bad Request The request was unacceptable, often due to missing a required parameter.
401 - Unauthorized No valid API key provided.
404 - Not Found The requested resource doesn't exist.
429 - Too many requests API request limit exceeded. See section Rate Limiting for more info.
5xx - Server Error We have failed to process your request. (You can contact us anytime)

You can always contact for support and ask for more assistance. We'll be glad to assist you with building your product.

Reviews

5.00
  • Review rating
  • Review rating
  • Review rating
  • Review rating
  • Review rating
API rating
Forrest Jordan
4 weeks ago

Forrest Jordan

  • Review rating
  • Review rating
  • Review rating
  • Review rating
  • Review rating

This API is great! It is very easy to use and has some very valuable data that I cannot find elsewhere.