BetBooster API (Batch Calls)

Modified on Thu, 29 Sep 2022 at 08:45 AM

How do we start? 

It’s simple. Follow the instructions below and if you have any questions, our team would be glad to assist on our support channels.                          


Customers that are consuming LSports data feed have the possibility to request tips within a batch of fixtures. Our first step begins with mappings. Once the integration begins, LSports team will make sure to send you a comprehensive file with the supported markets from each sport and their possible bet names. 


Once markets are mapped, please follow these instructions (Please note that the request will only work after whitelisting your Back-End IPs): 

Send a GET request to  


Prematch endpoint: 

https://betbooster-widget.lvision.io/api/v3/widgetapi/batchprematch?apikey={YOUR_APIKEY}&fixtureids={FIXURE_IDS_SEPARATED_BY_COMMAS}


Inplay endpoint: 

https://betbooster-widget.lvision.io/api/v3/widgetapi/batchinplay?apikey={YOUR_APIKEY}&fixtureids={FIXURE_IDS_SEPARATED_BY_COMMAS} 


The Query string would include the following parameters (only in English)


Parameters
Type
Optional / Required 
Description
apikey
String
required
Provided by LSports
fixtures
String
required
LSports’ fixtureIds separated by commas
lang
String
optional
For example: es / ru / de etc.  
Please follow these language codes http://www.lingoes.net/en/translator/langcode.htm 
English (en) is set as our default option.


The request will return an object with two fields - “batchGuid” and “insightsPerFixtureId”, the “insightsPerFixtureId” property will be an array of objects where each object represents tips for each match.


API Response body:

Field name 
Type
Description
batchGuid string
Batch identifier 
insightsPerFixtureId
array
An array of the tip’s metadata 


insightsPerFixtureId tip object:  


Field name 
Type 
Description
Insights
Array
Array of objects where each object represents a tip, check the table below in order to see the object properties. 
Type
string
Prematch/Inplay 
fixtureId
string
Unique identifier to this match on our side 
leagueId
string
Unique identifier for this league on our side 
warningCode
int
Numeric identification for warning code. 
description
string
Short text explaining the warning code. 
isSwapped
boolean
Will be true if the home and away team names are inserted in reversed order. 


The following properties will be included within the insights array: 

Field name 
Type
permanent / optional 
Description
MarketId
string
permanent
LSports’ market id - unique & permanent ID for each market.
Text
string
permanent
The tip’s text  
BetName
string
permanent
The recommended bet 
BetLine
string
optional
Relevant only for markets with lines such as Under/Over, Asian Handicap etc. 
tipId
number
permanent
LSports’ unique ID for each tip. 


*Please note that since home / away / league parameters are not sent to us, the text will contain placeholders that the customer will have to fill out on its own. 

For instance:

{ 
  "batchGuid": "0b791a82-1161-4d16-a708-636ae4beee84", 
  "insightsPerFixtureId": [ 
    { 
      "fixtureId": 7759975, 
      "type": "PreMatch", 
      "insights": [ 
        { 
          "marketId": 102, 
          "text": "{away} scored less than 3.5 goals in 11 of the last 15 matches.", 
          "betName": "Under", 
          "betLine": "3.5" 
        }, 
        { 
          "marketId": 16, 
          "text": "{away} scored first in 10 of their last 15 matches.", 
          "betName": "2", 
          "betLine": null 
        }, 
    ] , 
    "warningCode": 0, 
    "description": null 
    } 

Optional step - there are 2 parallel endpoints that can help you detect which fixtures have tips: 


Prematch link: 

https://betbooster-widget.lvision.io/api/v2/fixtures/prematch?apikey={YOUR_APIKEY}  

Inplay link: 

https://betbooster-widget.lvision.io/api/v2/fixtures/inplay?apikey={YOUR_APIKEY}


The response will contain a “responseGuid” property which is a unique identifier for the request and “IDs” property which will be an array of id`s - those IDs are the fixtures IDs that we provide tips for. 


For instance: 

{ 
  "responseGuid": "84286889-734d-419e-aeaa-2e60093e3eb9", 
  "ids": [ 
    7787115, 
    7756576, 
    7788392 
  ] 
} 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article