ParlayLegRequest
Properties
Name | Type | Required | Description |
---|---|---|---|
unique_leg_id | str | ❌ | Unique id of the leg. It's used to identify and match legs in the response. |
line_id | int | ❌ | Line identification. |
alt_line_id | int | ❌ | Alternate line identification. |
sport_id | int | ❌ | Sport identification. |
event_id | int | ❌ | Event identification. |
period_number | int | ❌ | This represents the period of the match. For example, for soccer we have: 0 - Game, 1 - 1st Half and 2 - 2nd Half |
leg_bet_type | ParlayLegRequestLegBetType | ❌ | Only SPREAD, MONEYLINE and TOTAL_POINTS are supported. |
team | str | ❌ | Chosen team type. This is needed only for SPREAD and MONEYLINE bet types. |
side | ParlayLegRequestSide | ❌ | Chosen side type. This is needed only for TOTAL_POINTS bet type. |
ParlayLegRequestLegBetType
Only SPREAD, MONEYLINE and TOTAL_POINTS are supported.
Properties
Name | Type | Required | Description |
---|---|---|---|
MONEYLINE | str | ✅ | "MONEYLINE" |
SPREAD | str | ✅ | "SPREAD" |
TOTAL_POINTS | str | ✅ | "TOTAL_POINTS" |
ParlayLegRequestSide
Chosen side type. This is needed only for TOTAL_POINTS bet type.
Properties
Name | Type | Required | Description |
---|---|---|---|
OVER | str | ✅ | "OVER" |
UNDER | str | ✅ | "UNDER" |
Build Your Own SDKs with liblab
Build developer friendly SDKs in minutes from your APIs