pybet365.response package¶

Submodules¶

pybet365.response.base module¶

Facade BaseResponse Object Delegation

Bet365 API Responses contain 2 common components

Bet365Response object is tasked to parse:

Further delegation for facade access to responses are subclassed

InPlayFilterResponse

InPlayOddsResponse

PreMatchOddsResponse

InPlayEventsResponse

UpcomingEventsResponse

The objects are accessible via dot notation or via .get(..)

class pybet365.response.base.Bet365Response(data: dict)[source]¶

Bases: dict

Base ResponseObject creator for Bet365 API Response.

success¶: Access for success.

class pybet365.response.base.FiResultBase(data: dict)[source]¶

Bases: dict

Component for dot notation for “FI” based objects.

>>> data = {
...     "FI":"87967884",
...     "event_id":"12312412",
...     "main": {}
... }

>>> FiResultBase(data).fi
>>> "87967884"

event_id¶: Access for event_id.

fi¶: Access for fi.

main¶: Access for main.

class pybet365.response.base.MetaBase(data: dict)[source]¶

Bases: dict

Component for dot notation for objects with “id” and “name”.

>>> data = {
...     "id":"10037409",
...     "name":"Mexico Liga MX Femenil"
... }

>>> MetaBase(data).id
>>> "10037409"

cc¶: Access for cc.

id¶: Access for id.

image_id¶: Access for image_id.

name¶: Access for name.

class pybet365.response.base.PagerBase(data: dict)[source]¶

Bases: dict

Component for dot notation access of pager object in API Response.

>>> data = {
...     "page": 1,
...     "per_page": 50,
...     "total": 730
... }

>>> PagerBase(data).page
>>> 1

>>> PagerBase(data).per_page
>>> 50

page¶: Access for page.

per_page¶: Access for per_page.

total¶: Access for total.

class pybet365.response.base.ResultBase(data: dict)[source]¶

Bases: dict

Component for dot notation access of results from any Endpoint.

>>> data = {
...   "id":"86576599",
...   "sport_id":"1",
...   "away":{
...       "id":"10361085",
...       "name":"Chivas Guadalajara Women"
...    },
...    "ss": None,
...    "our_event_id":"2130836",
...    "updated_at":"1581990232"
... }

>>> ResultBase(data).id
>>> "86576599"

>>> ResultBase(data).away.id
>>> "10361085"

away¶: Access for away.

home¶: Access for home.

id¶: Access for id.

league¶: Access for league.

sport_id¶: Access for sport_id.

ss¶: Access for ss.

time¶: Access for time.

time_status¶: Access for time_status.

class pybet365.response.base.StatsBase(data: dict)[source]¶

Bases: dict

Component for dot notation access of stats from any Endpoint.

>>> data = {
...     "event_id":"2130389",
...     "update_at":"1581990853",
...     "update_dt":"2020-02-18 01:54:13"
... }

>>> StatsBase(data).event_id
>>> "2130389"

>>> StatsBase(data).update_at
>>> "1581990853"

event_id¶: Access for event_id.

update_at¶: Access for update_at.

update_dt¶: Access for update_dt.

pybet365.response.in_play_events module¶

Facade for in_play_events Delegation

Bet365 API Responses contain 2 common components

Bet365Response object is tasked to parse:

This module provides delegation for InPlayEventsResponse

The objects are accessible via dot notation or via .get(..)

class pybet365.response.in_play_events.InPlayEventsResponse(data)[source]¶

Bases: pybet365.response.base.Bet365Response

Response Object Facade for InPlay Events Endpoint.

The object wraps the response and exposes dot notation access

The top level accesses for inplay endpoint are:

The results object is parsed into InPlayResult facades

Say you have a parsed response from InPlayEvents Endpoint

>>> response_object.results
>>> [
...     {
...         "type":"CL",
...         "CD":"1",
...         "FF":"",
...         "ID":"1",
...         "IT":"OV_1_1_9",
...         "NA":"Soccer",
...         "OR":"0",
...         "PC":"3"
...        },
... ]

>>> response_object.results[0].type
>>> "67890"

results¶: Access for results.

class pybet365.response.in_play_events.InPlayResult(data: dict)[source]¶

Bases: dict

Result Endpoint results array contents access.

type¶: Access for type.

pybet365.response.pre_match_odds module¶

Facade for pre_match_odds Delegation

Bet365 API Responses contain 2 common components

Bet365Response object is tasked to parse:

This module provides delegation for PreMatchOddsResponse

The objects are accessible via dot notation or via .get(..)

class pybet365.response.pre_match_odds.PreMatchOddsResponse(data)[source]¶

Bases: pybet365.response.base.Bet365Response

Response Object Facade for Result Endpoint.

The object wraps the response and exposes dot notation access

The top level accesses for upcoming endpoint are:

The results object is parsed into FiResultBase facades

Say you have a parsed response from UpcomingEvents Endpoint

>>> response_object.results
>>> [
...   {
...     "id": "67890",
...     "inplay_created_at": "1586461906"
...   },
... ]

>>> response_object.results[0].id
>>> "67890"

>>> response_object.results[0].inplay_created_at
>>> "1576465906"

results¶: Access for events.

pybet365.response.result module¶

Facade for upcoming_events Delegation

Bet365 API Responses contain 2 common components

Bet365Response object is tasked to parse:

This module provides delegation for ResultResponse

The objects are accessible via dot notation or via .get(..)

class pybet365.response.result.Result(data: dict)[source]¶

Bases: pybet365.response.base.ResultBase

Subclass of ResultBase with additional fields for Result endpoint.

>>> data = {
...   "id":"86576599",
...   "sport_id":"1",
...   "away":{
...       "id":"10361085",
...       "name":"Chivas Guadalajara Women"
...    },
...    "scores": {
...        "1": {
...            "home": "1",
...            "away": "2"
...        }
...    },
...    "updated_at": "1581990232"
... }

>>> Result(data).id
>>> "86576599"

>>> Result(data).away.id
>>> "10361085"

confirmed_at¶: Access for confirmed_at.

events¶: Access for events.

extra¶: Access for extra.

has_lineup¶: Access for has_lineup.

inplay_created_at¶: Access for inplay_created_at.

inplay_updated_at¶: Access for inplay_updated_at.

o_away¶: Access for o_away.

scores¶: Access for scores.

stats¶: Access for stats.

timer¶: Access for timer.

class pybet365.response.result.ResultEvent(data: dict)[source]¶

Bases: dict

Result Endpoint events array contents access.

id¶: Access for id.

text¶: Access for text.

class pybet365.response.result.ResultResponse(data)[source]¶

Bases: pybet365.response.base.Bet365Response

Response Object Facade for Result Endpoint.

The object wraps the response and exposes dot notation access

The top level accesses for upcoming endpoint are:

The results object is parsed into Result facades

Say you have a parsed response from UpcomingEvents Endpoint

>>> response_object.results
>>> [
...   {
...     "id": "67890",
...     "inplay_created_at": "1586461906"
...   },
... ]

>>> response_object.results[0].id
>>> "67890"

>>> response_object.results[0].inplay_created_at
>>> "1576465906"

results¶: Access for results.

pybet365.response.upcoming_events module¶

Facade for upcoming_events Delegation

Bet365 API Responses contain 2 common components

Bet365Response object is tasked to parse:

This module provides delegation for UpcomingEventsResponse

The objects are accessible via dot notation or via .get(..)

class pybet365.response.upcoming_events.UpcomingEvent(data: dict)[source]¶

Bases: pybet365.response.base.ResultBase

Component for dot notation access of results from UpcomingEvent Endpoint.

>>> data = {
...   "id":"86576599",
...   "sport_id":"1",
...   "away":{
...       "id":"10361085",
...       "name":"Chivas Guadalajara Women"
...    },
...    "ss": None,
...    "our_event_id":"2130836",
...    "updated_at":"1581990232"
... }

>>> UpcomingEvent(data).id
>>> "86576599"

>>> UpcomingEvent(data).away.id
>>> "10361085"

our_event_id¶: Access for our_event_id.

updated_at¶: Access for updated_at.

class pybet365.response.upcoming_events.UpcomingEventsResponse(data)[source]¶

Bases: pybet365.response.base.Bet365Response

Response Object Facade for UpcomingEvents Endpoint.

The object wraps the response and exposes dot notation access

The top level accesses for upcoming endpoint are:

The results object is parsed into UpcomingEvent facades

Say you have a parsed response from UpcomingEvents Endpoint

>>> response_object.results
>>> [
...   {
...     "id": "12345",
...     "our_event_id":"2294461",
...     "updated_at": "1586461906"
...   },
... ]

>>> response_object.results[0].our_event_id
>>> "2294461"

>>> response_object.results[0].updated_at
>>> "1586461906"

results¶: Access for results.

Module contents¶

Response namespace.

class pybet365.response.Bet365Response(data: dict)[source]¶

Bases: dict

Base ResponseObject creator for Bet365 API Response.

success¶: Access for success.

class pybet365.response.FiResultBase(data: dict)[source]¶

Bases: dict

Component for dot notation for “FI” based objects.

>>> data = {
...     "FI":"87967884",
...     "event_id":"12312412",
...     "main": {}
... }

>>> FiResultBase(data).fi
>>> "87967884"

event_id¶: Access for event_id.

fi¶: Access for fi.

main¶: Access for main.

class pybet365.response.InPlayEventsResponse(data)[source]¶

Bases: pybet365.response.base.Bet365Response

Response Object Facade for InPlay Events Endpoint.

The object wraps the response and exposes dot notation access

The top level accesses for inplay endpoint are:

The results object is parsed into InPlayResult facades

Say you have a parsed response from InPlayEvents Endpoint

>>> response_object.results
>>> [
...     {
...         "type":"CL",
...         "CD":"1",
...         "FF":"",
...         "ID":"1",
...         "IT":"OV_1_1_9",
...         "NA":"Soccer",
...         "OR":"0",
...         "PC":"3"
...        },
... ]

>>> response_object.results[0].type
>>> "67890"

results¶: Access for results.

class pybet365.response.InPlayResult(data: dict)[source]¶

Bases: dict

Result Endpoint results array contents access.

type¶: Access for type.

class pybet365.response.MetaBase(data: dict)[source]¶

Bases: dict

Component for dot notation for objects with “id” and “name”.

>>> data = {
...     "id":"10037409",
...     "name":"Mexico Liga MX Femenil"
... }

>>> MetaBase(data).id
>>> "10037409"

cc¶: Access for cc.

id¶: Access for id.

image_id¶: Access for image_id.

name¶: Access for name.

class pybet365.response.PagerBase(data: dict)[source]¶

Bases: dict

Component for dot notation access of pager object in API Response.

>>> data = {
...     "page": 1,
...     "per_page": 50,
...     "total": 730
... }

>>> PagerBase(data).page
>>> 1

>>> PagerBase(data).per_page
>>> 50

page¶: Access for page.

per_page¶: Access for per_page.

total¶: Access for total.

class pybet365.response.PreMatchOddsResponse(data)[source]¶

Bases: pybet365.response.base.Bet365Response

Response Object Facade for Result Endpoint.

The object wraps the response and exposes dot notation access

The top level accesses for upcoming endpoint are:

The results object is parsed into FiResultBase facades

Say you have a parsed response from UpcomingEvents Endpoint

>>> response_object.results
>>> [
...   {
...     "id": "67890",
...     "inplay_created_at": "1586461906"
...   },
... ]

>>> response_object.results[0].id
>>> "67890"

>>> response_object.results[0].inplay_created_at
>>> "1576465906"

results¶: Access for events.

class pybet365.response.Result(data: dict)[source]¶

Bases: pybet365.response.base.ResultBase

Subclass of ResultBase with additional fields for Result endpoint.

>>> data = {
...   "id":"86576599",
...   "sport_id":"1",
...   "away":{
...       "id":"10361085",
...       "name":"Chivas Guadalajara Women"
...    },
...    "scores": {
...        "1": {
...            "home": "1",
...            "away": "2"
...        }
...    },
...    "updated_at": "1581990232"
... }

>>> Result(data).id
>>> "86576599"

>>> Result(data).away.id
>>> "10361085"

confirmed_at¶: Access for confirmed_at.

events¶: Access for events.

extra¶: Access for extra.

has_lineup¶: Access for has_lineup.

inplay_created_at¶: Access for inplay_created_at.

inplay_updated_at¶: Access for inplay_updated_at.

o_away¶: Access for o_away.

scores¶: Access for scores.

stats¶: Access for stats.

timer¶: Access for timer.

class pybet365.response.ResultEvent(data: dict)[source]¶

Bases: dict

Result Endpoint events array contents access.

id¶: Access for id.

text¶: Access for text.

class pybet365.response.ResultResponse(data)[source]¶

Bases: pybet365.response.base.Bet365Response

Response Object Facade for Result Endpoint.

The object wraps the response and exposes dot notation access

The top level accesses for upcoming endpoint are:

The results object is parsed into Result facades

Say you have a parsed response from UpcomingEvents Endpoint

>>> response_object.results
>>> [
...   {
...     "id": "67890",
...     "inplay_created_at": "1586461906"
...   },
... ]

>>> response_object.results[0].id
>>> "67890"

>>> response_object.results[0].inplay_created_at
>>> "1576465906"

results¶: Access for results.

class pybet365.response.UpcomingEvent(data: dict)[source]¶

Bases: pybet365.response.base.ResultBase

Component for dot notation access of results from UpcomingEvent Endpoint.

>>> data = {
...   "id":"86576599",
...   "sport_id":"1",
...   "away":{
...       "id":"10361085",
...       "name":"Chivas Guadalajara Women"
...    },
...    "ss": None,
...    "our_event_id":"2130836",
...    "updated_at":"1581990232"
... }

>>> UpcomingEvent(data).id
>>> "86576599"

>>> UpcomingEvent(data).away.id
>>> "10361085"

our_event_id¶: Access for our_event_id.

updated_at¶: Access for updated_at.

class pybet365.response.UpcomingEventsResponse(data)[source]¶

Bases: pybet365.response.base.Bet365Response

Response Object Facade for UpcomingEvents Endpoint.

The object wraps the response and exposes dot notation access

The top level accesses for upcoming endpoint are:

The results object is parsed into UpcomingEvent facades

Say you have a parsed response from UpcomingEvents Endpoint

>>> response_object.results
>>> [
...   {
...     "id": "12345",
...     "our_event_id":"2294461",
...     "updated_at": "1586461906"
...   },
... ]

>>> response_object.results[0].our_event_id
>>> "2294461"

>>> response_object.results[0].updated_at
>>> "1586461906"

results¶: Access for results.