Betradar - the betting arm of Sportradar

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
topOfPage
topOfPage
Excerpt Include
HideElements
HideElements
nopaneltrue

Excerpt Include
BetradarLogo
BetradarLogo
nopaneltrue

Panel
Tip

Tip

Disconnection and recovery handling is handled automatically by the SDK. Please refer to this THIS section, if you're using the SDK.

In case of an incident (a disconnection, maintenance on Betradar's side, etc.) we provide you with a few endpoints on the API that trigger sending of recovery messages in the feed.
There are a few possible situations where recovery is needed:

  • first First run (subscription to a producer)
  • connection Connection issues
  • maintenance Maintenance on Betradar's side (alive messages with subscribed = 0)
  • maintenance Maintenance on clientyour's side

API endpoints

  • full Full odds recovery (only used for initial connection or in case of a disconnection longer than 72 hours)
  • recovery Recovery since after timestamp (max. for the past 72 hours)
  • recover Recover odds for a specific sport event
  • recover Recover stateful messages for a specific sport event


Warning

Warning

There is a limitation on how many recovery requests you can send to the server. More information can be found here - https://docs.betradar.com/display/BD/UOF+-+Access+restrictions+for+odds+recovery

Procedure

A client should always store the last successfully received alive message (or its timestamp) from each producer. In case of a disconnection, recovery since after timestamp should be issued for each affected producer, using the timestamp of the last successfully processed alive message before issues occurred.

Info

More information about recovery procedures and options can be found here - https://docs.betradar.com/display/BD/UOF+-+Recovery+using+API

HideElements
cssselectortd.attachment-created.modified-column
metastrue
peopletrue
toolstrue