-
Notifications
You must be signed in to change notification settings - Fork 56
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
Result after placing a Bet #13
Comments
No partial stake, the whole bet will have the requested odds OR be accepted at better odds. The bet response should have the final odds that the bet was accepted at. When placing the bet request there is a setting named something like "acceptBetterOdds", if that's true then your bet might be accepted at better odds in case the line moves. If it s false your bet is only accepted if the line didn't move |
Either way it s an all or nothing thing, no partial bets |
Ok, no partial bets no splitted bets, thank you, good to know so it's a simplier managment than in betting exchange. Would you have a code example of placing a bet with the "acceptBetterOdds" parameter set to true? Thanks about the other issue related to calls delay. Just to confirm (because the issue is closed, in the context if automated betting, i suppose we should introduce a delay between the calls, what do you think of? Anyway do you confirm there is actually no delay managment in the wrapper? |
Correct no built in delay mechanism in the Wrapper so you have to manage the delays yourself. Also the delays are never for placing bets, they ll be happy if you place bets non stop :) It s really about the other Api calls. Especially if you make calls frequently without providing the "since" parameter, that will get you closed quickly. |
As for the acceptBetterOdds, I don't have code sample handy, on my phone now, but all you need to do is toggle to true the boolean in your bet request, see here: https://github.com/harveysburger/pinnaclewrapper/blob/master/PinnacleWrapper/Data/PlaceBetRequest.cs |
This one here
|
Lol yes placing bets non stop ahaha they would surf on pleasure and would fire the one who would introduce a limitation on that :) Well about the since, : with the since parameter must be restricted to once every 5 seconds while without it's 60 seconds so i think they would be more unhappy if you call frequently the second one which consue more resources on their end :) Anyway, in an automated trading context, i should ad some delays betwee those kind of lines :
Yes i saw in the netcore wrapper release (allowing to access the source), it was acceptBetterLine instead of acceptBetterOdds, it's just that as i begin in c#, i'm not sure how to make the PlaceBetRequest call yet, reason why a code line example would be useful for starters like me. I mean, i suppose this would looks something like : As for the PlaceBetResponse, i don't see the syntax, ie how to catch the result with |
I'll dig up something, but in short you have the right idea, instantiate a new betrequest object and fill in the details of every properties, or most of them anyway, then pass it to api.PlaceBet Your var placebet should have the response. I am still on my phone so can't really confirm the details tonight |
That would be very cool, this is clearly the kind of things that help to understand and teach how to use a given resource (here pinaclewrapper) because you discover the articulation and the logic behind the points you're blocking on at a given moment in time. Thanks for the info about the delayed info on live events, i would not have expected that (one more things matchbbok does not work that way, the other one was about the live event parameter which is much more logic on matchbook in my eyes). Yep, phones are useful to discuss but contrary to what we see in the movie, are short to really dive into the matrix :) |
Hi, Any update? |
Hello Harvey, Did you get something about a PlaceBetRequest example and how to change the value of acceptBetterLine as well? Thanks in advance |
Hi, haven't had a chance to write some examples, on vacation now but next week I'll put something together |
Hi, |
hey, nah nothing too exotic , stayed in my country :) btw I submitted a simple example of how to place a bet. Nothing fancy the code just picks a random moneyline market and places a small bet on it. I dont plan on writing any specific documentation for the wrapper since it just mimics almost everything from the Pinnacle API so the best is just relying on https://pinnacleapi.github.io/betsapi#operation/Bets_Straight to see what stuff means and what the various requests and responses have |
Thank you Harvey, |
Hello Harvey,
But with debug, it helps to understand the intuitive parts. By "PeriodStatus", do you mean their lookups period number https://www.ps3838.com/static/index.php/en-us/help/api-user-guide-en-us#PeriodNumberLookup? I found MoneyLine.Home (in our lines object structure) but what does mean About In the place bet request itself, we have What is the importance of |
Hello,
I don't know yet how the pinnacle/ps3838 process work and how it's handled by the wrapper.
When we place a bet, it’s accepted or rejected but if accepted, is it accepted as is? ie with the submitted stake at the given odd OR can we have as a result a partial stake accepted at the given odd OR several splitted accepted stakes at differents odds?
The text was updated successfully, but these errors were encountered: