Our company offers a collection of data feeds containing fixtures and odds from a variety of bookmakers worldwide. At this time the offer includes 32 bookmakers with worldwide coverage on all Soccer leagues, the US sports (Football, Basketball, Baseball, Hockey), horse and dog racing as well as a variety of other sports. We provide about 40,000 different markets including Match odds, Asian handicaps, scores, totals, spreads/margins as well as many other team, player, goal and score markets.
We charge a simple monthly fee for any data access regardless of type of API, number of API calls, data transfer, number of sports/leagues/markets accessed or available bookmakers. All prices are expressed in EUR and are exempt from VAT and sales tax. Note that we may enforce limits on API calls per day or month to prevent our data from being leaked.
At this time our service does not include results, statistics, H2H information. All data is to be considered pre-game.
Our data is organized in 3 groups of objects:
- Markets – contain the sport, league, event name, start date and time, bet type and status;
- Selections – contain the name of the selection;
- Offers – contain foreign keys to market, selection, bookmaker, time stamp, current price and last known price.
You can query our API for either objects and include as many filters as required.
Below are three visual representations of MySQL database tables we would recommend for data storage:
Since each table contains several million records, we feel we should mention that a typical setup should include a decent database server with an intermediary Memcache cluster. On a simple test we were able to run about 50 complex queries per second (grouped joins across all 3 tables).
The box in the example below is a dual core Xeon running at 2300 Mhz with 8 Gb of Ram, with MySQL 5.1 and InnoDb as storage engines. Indexes were created on all keys. In our setup we have used a cluster of 4 Memcache servers with 2Gb of RAM each and cache expiration set from 1 to 5 minutes for various chunks of data, hence the spike-ish nature of the CPU usage graph. Without using Memcache the graphs are somewhat parallel and CPU usage is about 25% higher while query latency can grow by up to 40%.
Queries per second
Frequently asked questions
What data do you offer?
We offer sports, leagues, fixtures (schedules), bet types and bets (lines) including current odds.
Is the data delayed?
Due to the nature of the data, sources and the way the data is transferred and replicated there are always delays that vary from a few seconds to a few minutes, regardless of market, provider, transfer method. Even if some providers advertise real-time or streaming data, there are no real-time transmissions nor a way to get this data with zero delays, there are always some delays and communication protocol latency. See below the data sources and all steps taken before data reaches you.
- Events are played all over the world
- Each event is viewed by a number of scouts that enter scores, plays, team information and so on
- Scouting agency collects data from scouts with a few seconds delay
- Scouting agencies send data to providers, where data is categorized, grouped and broadcasted to data providers, this takes seconds to minutes
- Books purchase data from providers, data is downloaded and updated with a few seconds delay
- Books make data available on their websites with more delays
- It then takes us seconds to several minutes to download data from books
- We process, group and categorize data, a process that can take 1-30 seconds
- API clients download data from our database on an as-needed basis (further variable delays)
Do you offer live data as well?
At this time we do not offer live data, however it is planned so please check back soon.
Do you offer play by play updates?
Do you offer league tables?
Can this data be used to effectively run a book?
Can this data be used for risk management, arbitrage, matched betting or odds comparison?
Can we re-sell your data to 3rd parties?
Not under any circumstances.