A second feed for when your main one goes down

Why operators run a second feed

Every feed has bad moments: a provider outage, a busy Saturday, a network problem between you and them. With one feed, the safe move is to suspend everything until it comes back, and customers leave while your markets are closed.

A second feed changes that. When the main feed goes quiet, your platform switches the affected events to the backup and keeps taking bets. Most backup feeds are sold like main feeds, with a contract and a price to match; ours is self-serve and monthly.

What the backup gives you

• Pre-match and live odds, one priced line per market, each outcome open or suspended as it changes.
• Scores, periods and the clock, so you can check that both feeds agree.
• Settlement, so bets taken on the backup's prices can be graded on its results.
• A heartbeat every 10 seconds on the WebSocket and a /status call: you know at once whether the backup itself is healthy.

How to set it up

1. Map events once: match our events to your main feed's by teams, league and start time, and keep the link. Our ids stay the same from upcoming to live to closed. The mapping guide explains the market dictionary and team ids.
2. Keep the socket open all the time, so the backup is warm when you need it.
3. Switch on a rule you set: for example, when your main feed has sent nothing for an event for a few seconds while ours is live.
4. Switch back when the main feed recovers; settle each bet on the feed whose price it was taken on.