Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to deal with variant markets and outrights? #17

Open
namreg opened this issue Dec 14, 2020 · 4 comments
Open

How to deal with variant markets and outrights? #17

namreg opened this issue Dec 14, 2020 · 4 comments

Comments

@namreg
Copy link

namreg commented Dec 14, 2020

According to the code, these features are not supported. Is it true?

@ianic
Copy link
Contributor

ianic commented Dec 20, 2020

Variant markets are treated as ...a variant of market.
Non variant markets have just MarketID, and 0 for VariantID. Variant markets has non-zero VariantID.
They are working just fine.

Can you please explain the outrights needs a little bit.

@namreg
Copy link
Author

namreg commented Dec 30, 2020

Variant markets are treated as ...a variant of market.
Non variant markets have just MarketID, and 0 for VariantID. Variant markets has non-zero VariantID.
They are working just fine.

Under variant markets I mean markets that have variant specifier. According to the Betradar docs, to get market name and it's outcomes we should make additional request.
CleanShot 2020-12-30 at 13 12 45@2x

Can you please explain the outrights needs a little bit.

Betradar can provide odds for such events as outrights (stage, simple_tournament, season). To fetch fixtures for these entities we need to call another http route. Currently sdk expects that fixture will always be match.

@ianic
Copy link
Contributor

ianic commented Jan 13, 2021

Each received odds change message is analyzed and additional api request is made for any variant market found.

@ianic
Copy link
Contributor

ianic commented Jan 13, 2021

Similar each fixture change message can trigger api request for that fixture.
Api request is going to: api.betradar.com/v1/sports/{{.Lang}}/sport_events/{{.EventURN}}/fixture.xml. It could be that in response from that url is enough information to handle outrights also. Please check, I don't remember any more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants