Feeds
We recommend storing a snapshot of received information in a cache or database on your side as well as storing revision for recovery. In case of recovery you will only receive snapshots for data which have changed after the specified revision which means that old finished events may not be recovered.
One message in the feed can have multiple deltas, which should be consumed in ascending order of revision number, otherwise event(s) may have incorrect status.
Feed recovery from 0 revision should happen as rarely as possible. It is a slow process which consumes a lot of resources.
Each feed should be considered as a separate entity/integration. They can become not accessible or drop connection independently from each-other so we don’t recommend starting full system recovery in case of some specific feed disconnected.
Feeds are not synchronised with each-other meaning that some information may become available from one feed and arrive with delay from another feed.
Example: event metadata can arrive through metadata feed before the event actually sent through delta feed.
The integration involves connecting to four essential feeds:
Delta Feed
The most critical feed, providing essential information such as event fixtures, event changes, markets, and scoreboards.
Metadata Feed
Supplies event-specific metadata, particularly useful for racing sports (e.g., horse racing, harness racing, greyhound racing).
Ticket Settlement Feed
Provides bet settlements on ticket level.
Translations Change Feed
Notifies you about changes in our translation data.
Can be used in pair with our translation API endpoints to keep the data in sync.
Last updated