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.
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. For your convenience, the markets will be elaborated both in names and Ids.
Once markets are mapped, please follow these steps:
Send a GET request to https://betbooster-widget.lvision.io/api/v3/widgetapi/prematchtips or https://betbooster-widget.lvision.io/api/v3/widgetapi/inplaytips (Please note that the requests will only work after whitelisting your Back-End IPs)
The Query string would include the following parameters (only in English)
Parameters | Type | Optional / Required | Description |
home | String | required | Name of the home team / player |
away | String | required | Name of the away team / player |
date | String | required | “dd/MM/yyyy HH:mm” format. |
sport | String | required | Football/Basketball etc... |
cid | String | required | Unique user identifier For example: 1188 |
apikey | String | required | Provided by LSports |
lang | String | Optional | Please follow this list: http://www.lingoes.net/en/translator/langcode.htm |
originHome | string | Optional | The name of the home team in your requested language |
originAway | string | Optional | The name of the away team in your requested language |
originLeague | string | Optional | The name of the league (in which the match is being played) in your requested language |
For instance:
https://betbooster-widget.lvision.io/api/v3/widgetapi/prematchtips?home=Azerbaijan&away=Belgium&date=10/11/2021%2018:00&sport=football&apikey={YOUR_APIKEY}&cid=hj34hvb0145l7 (where %20 stands for a space)
https://betbooster-widget.lvision.io/api/v3/widgetapi/inplaytips?home=Azerbaijan&away=Belgium&date=10/11/2021%2018:00&sport=football&apikey={YOUR_APIKEY}&cid=hj34hvb0145l7 (where %20 stands for a space)
Those are the fields that would be included in the response data
API Response body
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 |
warningCode | int | Numeric identification for warning code |
description | string | Short text explaining the warning code |
*Successful requests that contain tips will have warning code: “0” and description: “null”.
This object contains an array of the tips possible under the criteria set within the request
Insight objects
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 |
This is the full list of potential warning codes:
Warning Name | Warning Id | Description |
NoWarning | 0 | Tips were transferred properly (NULL) |
NoFixtureMapping | 1 | Please check team names and start date |
NotSupported | 2 | No LSports Fixture |
WrongRouteForAPI | 3 | Please use PreMatch link / Please use InPlay link |
NoPrematchBundle | 4 | No PreMatch bundle |
NoInplayBundle | 5 | No InPlay bundle |
NoSportBundle | 6 | SportId {sportId} is not allowed with ApiKeyId = {apikeyId} |
NoCustomerSettings | 7 | Customer Settings not found or empty |
NoSelectedCustomerSettings | 8 | Selected Customer Settings {apikeyId} not found |
NoSupportedMarkets | 9 | Markets not supported for that client.{marketIdsList} |
NoTips | 10 | No tips available |
NoSportsMapping | 11 | Please Check sport name |
NoCorrectDateFormat | 12 | Please Check date input (dd/MM/yyyy HH:mm) |
NoMappingResponse | 13 | No response from mapping server |
For instance:
{ "fixtureId": 7751989, "type": "Inplay", "insights": [ { "marketId": 2, "text": "Once tied at the 15th minute, 8 of these last 10 FK Rad Beograd's matches resulted with less than 3.5 goals.", "betName": "Under", "betLine": "3.5", "tipId": "cbe98cf5-c122-2152-8b7c-f8f3b430782a" }, "marketId": 16, "text": "FK Rad Beograd conceded first in 9 of their last 15 matches.", "betName": "1", "betLine": null, "tipId": "ggq95cf5-c982-3142-8a7c-f8f3b430793b" }, ], "warningCode": 0, "description": null }
Collecting data regarding user engagement
In order to analyze the data on your punters’ patterns and process it through our personalization engine, we would like your assistance in delivering this data back to us.
- Send a POST request to https://betbooster-widget.lvision.io/api/v3/events/betslip
- The Query string should include the following parameters (only in English)
Parameters | Type | Optional / Required | Description |
timestamp | int | Required | UTC timestamp |
Cid | string | Required | Unique user identifier, for example: 1188 |
fixtureId | int | Required | Unique fixture identifier, for example: 1234 (will be provided by LSports) |
apikey | string | Required | Unique customer identifier, for example: 5678 |
tipId | string | Required | Unique customer identifier, for example: 5678 (will be provided by LSports) |
language | string | Required* | Required only for languages other than English. |
Odds | string | Required | For example: 1.72 |
oddsType | string | Required* | Required only for formats other than Decimal. |
insightSelected | string | Required | Does the tip’s recommendation was added to BetSlip or not (true/false in lower case) |
betCompleted | string | Required | Does the BetSlip with the tip’s recommendation eventually placed (only true/false in lower case) |
*Please note that each action by user should trigger a request with the information above
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article