API Roadmap Survey

[Bohan123]

Hi,

I want to fetch GPS data for horse race events via API. Is there any API endpoint for this?
Any method other than API to get the GPS data is also appreciated.

I have tried this (ref image "req") using postman and got a response(ref image "resp" ). Is this the correct endpoint to connect to and if yes, please let me know how i can get a session token and id mentioned in the body of the request in the attachment "req".

[ColinHunter]

Id love to see more flexible BSP betting, where we can pass in a range of acceptable BSP prices, not just a max / min depending on if you're on the back or lay side!

[tradernz]

Hey Liam yeh that's been my gospel to get started.... totally something along those lines but with abit more examples around best practise and details around the difference between the streaming data etc

[LiamP]

I'd love more code examples using things like betfairlightweight .. they have built an amazing platform and would love more examples

Hey, you checked out the Betfair aus site?

https://betfair-datascientists.githu...ythontutorial/

[tradernz]

I'd love more code examples using things like betfairlightweight .. they have built an amazing platform and would love more examples

[RothNorton]

In regards to tarbs post:
https://forum.developer.betfair.com/...6054#post26054


-I would also appreciate a filter which controls how far out to return markets.

-I would also like it if more data were returned (optionally) in the market stream.
Basically whenever a change comes in, we need to know at least:

EventType Id and Name,
Event Id and Name and StartDate etc.
Market Id and Name and StartDate, Status etc. and all Runners
Runner Id and Name

Basically we need most of the data provided through the betting api, through calls to listX

-As well, this data should also be included the order stream, as that only returns a market id, and depending on how you're program works, if you want the full data you also need to do a few calls to the betting api, to match up the order with the market details.

Obvs this data wouldnt have to be sent on a delta.

[tarb]

Absolutely not. Streaming is for data changes upto 20 times or so a second, like the price and amount available.
The horses names ect... are static data and only need to be called once.

Strongly disagree with you. The streaming api already supports market definitions which contain static non changing information (like venue, timezone, regulator, countrycode ..etc) - all of which could be retrieved from calling list market catalog. The distinctions between including this static data and market and runner name seems entirely arbitrary. If people don't want this information they already have the option of not requesting it. I imagine there are a lot of people, like myself, who call list market cat, only for these names. (Also its not entirely static as horses can be scratched and added whilst a market is ongoing requiring detection and retrieval of the new name).

Not to mention that pairing data from two sources adds another level of developer complexity and opportunity to introduce errors, is far more inefficient for both Betfair to have to serve and for applications to retrieve. And for what? To reduce the image payload size of a market by ~2%?

I can literally not see any argument for it not being included. Very small increase in payload size, but the people who care about that wont be after the market definitions anyway.

PS (im not against runner metadata being included, tho it probably should go under a new flag)

[newbie99]

Having two factor authentication optional for log in .

Horse Racing GPS feed ;
In Play betting is a point of difference that Betfair can offer their clients. Having applications that can level the playing field against on track players can only be good.

This would open up a world of possibilities!

Is there any update on what decision was made with regards to the next update?

[LetsGo]

Voted Other - Would like to use my vote to the adding of market and runner names in the Stream API as I also need to make calls to listMarketCatalogue just to get them. In addition there is a lot of very useful runner data in the runnerMetadata returned by listMarketCatalogue (previous form, days since last run, offical rating, weight, etc) that would be good to have as in the stream API. As this information does not change for the life of the market perhaps it could be returned only for images and optional via a flag like it is in listMarketCatalogue.

Absolutely not. Streaming is for data changes upto 20 times or so a second, like the price and amount available.
The horses names ect... are static data and only need to be called once.

[drazor25]

Voted Other - Would like to use my vote to the adding of market and runner names in the Stream API as I also need to make calls to listMarketCatalogue just to get them. In addition there is a lot of very useful runner data in the runnerMetadata returned by listMarketCatalogue (previous form, days since last run, offical rating, weight, etc) that would be good to have as in the stream API. As this information does not change for the life of the market perhaps it could be returned only for images and optional via a flag like it is in listMarketCatalogue.

[jptrader]

I suggest that you extend RunnerStatus (https://docs.developer.betfair.com/d...s-RunnerStatus) to include more information about the final status of a runner. Right now, it does not reflect the statuses that can be obtained on e.g. Football Asian Handicap /Draw No Bet/ Goal Lines markets etc, where a runner can have a final status of not just Winner or Loser, but also Void, HalfWinHalfVoid or HalfLoseHalfVoid. This information is currently unavailable from the API, and users must know the final score (also still unavailable from the API) to track this.

[bfexplorer]

It would be interesting if it would be possible to add a label to a bet while placing a bet (for example A or B etc).

After this the label should be visible in the bet history for every bet. This would make it easier to link bettingstrategies to results.

That is already implemented, read api doc.

[Mike123]

It would be interesting if it would be possible to add a label to a bet while placing a bet (for example A or B etc).

After this the label should be visible in the bet history for every bet. This would make it easier to link bettingstrategies to results.

[bfexplorer]

Football meta data are already offered by web api, well not documented but accessible, therefore I would really like to see implementation of Graphs API, what you actually already promised to implement.

To the football meta data, I have got following question:

How you manage VAR decisions on top leagues in Europe they already use it in couple leagues, I watched El Clasico yesterday and VAR was used .

You should suspended market till VAR decision is not known, that did not happen in many matches in last days, I noticed such situation when testing some football strategy:

http://bfexplorer.net/Community/BlogContent/382

on SPAL - Frosinone match, at 32 minute of the match it was reported 0 - 1, then later in next minute the score was fixed to the right one: 0 - 0.

[LetsGo]

I would like to have access to the "Cash Out" option from the api.