Versions Compared

Version Old Version 14 New Version 15
Changes made by

Mikk Sillaste

Mikk Sillaste

Saved on

Key

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

...

Bet Feed Receiver API

Overview

Swagger documentation https://docs.uat.risk.api.geniussports.com/#/Resources/SendBets

Once bets have been confirmed as placed or the status of the already placed bet is changed then the request should be sent to the Bet Feed Receiver. This is an HTTP REST API that expects to receive bet data in JSON format, as a body of an HTTP POST request.Swagger documentation https://docs.uat.risk.api.geniussports.com/#/Resources/SendBets

Data flow requirements

  • The bookmaker’s bets must be delivered to the API within 5 seconds of their placement. Violating this requirement may lead to outdated liability values, thus incorrect Bet Assessment API responses.

  • Timestamps are required for sequencing during peak betting loads.

  • If the state of the bet changes, the full updated bet state should be resubmitted to the Bet Feed Receiver.

  • It is required to resubmit the bet if any of the bet legs was settled or cancelled.

  • It is required to populate a Bet's Payout field for fully settled bets (all legs are settled) and fully cancelled bets (the whole bet is cancelled).

  • For Multi and System Bets it is important to resubmit the bet state when any of the legs are settled, with the new Leg Status and its PayoutPrice. Updates should be sent until all legs of the multi and system bet have been settled.

  • The sender is responsible for the retry of failed API calls.

...