Choosing a sportsbook feed: the questions to ask, answered
What operators ask any odds feed provider before they sign, and our answers, each with the docs that back it.
-
Does it cover my sports and leagues?
The feed carries 15 sports and 2,277 competitions, read from its live catalogue, not a brochure. Every sport has its own page with its competitions and most priced markets. Coverage by sport →
-
How many markets does an event carry?
The full market list of each event, not a dozen main lines: handicaps, totals, halves and periods, player and prop markets where they are priced, with new lines added in play. Each market comes with its order and groups, so you can lay out an event page. Markets and mapping →
-
Are suspensions sent, or do markets just disappear?
Each outcome is open, suspended or closed, and every change is pushed on the WebSocket as it happens. A market the source pauses stays on the event as suspended and reopens under the same ids. A feed status (
up,stale,down) on REST and every 10 seconds on the socket tells you when to stop taking bets altogether. Event lifecycle → -
Who settles the bets, and when?
The feed does: each outcome gets won, lost or void (a push is void: stake back) as the match decides it, so many markets settle during play. Results are pushed on the WebSocket and listed over REST. Nothing is voided just because time passed: an outcome without a result stays pending. Settlement →
-
What if a result is wrong?
A result taken back comes as a withdrawn result (pending), then the new one when it is settled again. Apply each settlement row once, by its id, and your payouts follow. Withdrawn results →
-
Do ids stay the same?
Yes. Sports, countries, leagues, teams and the market dictionary have stable ids; an event keeps one id from pre-match to live to closed, postponed and abandoned matches included. Map them to yours once. Mapping →
-
What happens after a disconnect?
Every socket message carries a sequence number. A gap, or a reconnect, is caught up with two REST calls: events changed since your last message, and settlements since your last id. Then the socket goes on from the number the catch-up gives you. Recovery →
-
How is the data delivered?
REST (JSON) for snapshots and catch-up, and a WebSocket that speaks the Pusher protocol, so any Pusher client in any language works. One channel carries every sport; new objects come whole, changes come short. WebSocket →
-
How fast is it?
We publish no latency figure until our monitoring measures one. Measure it yourself on your own events: the 14-day free trial is full Pro, so test it on a busy Saturday or Sunday evening. Start 14-day trial →
-
What are the limits?
One key per account, working from one allowed IP; 120 REST requests a minute; 2 sockets per key (a third closes the oldest); 30 days of settled history. The same in the trial and paid. Limits →
-
What does it cost, and is there a contract?
One plan: $750 a month or $7,500 a year (2 months free), paid in Bitcoin. No contract, no setup fee, no minimum term: to stop, do not renew. Pricing →
-
Can I try it before paying?
Yes: a 14-day free trial of full Pro, once per company, starting at your key's first API call (not at signup). Every event, REST and WebSocket, settlement included. Before that, the live and settled boards on this site are open with no signup. How the trial works →
-
Are you a rights holder? Who holds the licence?
We are a data feed, not a rights holder, and we make no rights claims. We supply businesses and take no bets; your licence in your market stays your obligation. Terms →
-
Can I resell it?
No. Use the data in your own products and operations (show it, price and settle bets, run your sportsbook or app); reselling or passing on the feed itself is not allowed. Terms →
-
Is there an uptime SLA?
Not at launch. The feed status is on
GET /v1/statusand on the socket every 10 seconds, so your systems know when to suspend. Best practices →
Other ways teams use the feed
Sportsbook feed
What a sportsbook needs from a data feed: menu, fixtures, markets with live odds, scores and bet settlement over REST and WebSocket. $750 a month, no contract.
Bet settlement API
Settle bets automatically: each outcome pending, then won, lost or void as the match decides it, pushed on the WebSocket and over REST. No grader to write.
Backup odds feed
Keep your markets open when your main sportsbook feed drops: a second feed with fixtures, markets and odds, scores and settlement, $750 a month, no contract.
Crypto sportsbook feed
A sportsbook feed you pay for in crypto: fixtures, markets and odds, scores and settlement over REST and WebSocket, no bank, no contract, from any country.
Start a sportsbook
What a new sportsbook needs from a data feed, what stays your platform, and how to go from a trial key to live in days, not months.
Odds for bots and apps
Pre-match and live odds, scores and results pushed over WebSocket for Telegram bots, tipster tools and betting apps. A 14-day free trial.