Tabcorp Digital API REST -- 2

Hi, I would like something like below but need to: (1) login (2) return full market details(prices) for both the win and place markets of a particular race, perhaps win market to excel sheet 1 and place market to excel sheet 2, as well as the time the race is scheduled to run. (3) allow the ability to move to the next or later races once I have finished with the current race (4) enable placement of win bets from spreadsheet (5) refresh as quickly as possible, given Tabcorp limitations. (6) be able to run continuously, perhaps hibernate when there are no races [login to view URL] (7) I can write the VBA code to make the betting decisions, but my VBA code will need access, as stated above, to being able to go to a new market, as well as place a [login to view URL] an example, I currently use Betting Assistant for Betfair which has such excel interface capability. [login to view URL] I don't need all the functions of Betting Assistant, just the functions stated above. Regards, Bob Hart Want the data from the Tabcorp TAB site to populate an Excel [login to view URL] Digital API REST CEEJAY67 2 days ago REST The new Tabcorp API is based on Representational state transfer. Among other things, it values 2 major principles. Simplicity The new API embraces the notion of resources and URIs. For example https://.../sports represents the list of all sports https://.../sports/Rugby%20League represents everything about Rubgy League https://.../sports/Rugby%20League/competitions represents all Rubgy League competitions This makes the API easy to discover and navigate. Similarly, for account management: https://.../accounts/123 represents your TAB account https://.../accounts/123/statement represents your TAB account statement Resources support one or more of the standard HTTP verbs, with the following semantics: GET returns the given resource. It is guaranteed to have no side-effect, and is most-likely cacheable. POST creates a new resource. Be careful: posting several times will create multiple resources. PUT modifies an existing resource. This is an idempotent operation, and can be executed several times. DELETE deletes an existing resource, which is also idempotent. For a concrete example: GET https://.../accounts/123 returns all your account details GET https://.../accounts/123/credit-cards returns the list of your credit cards POST https://.../accounts/123/credit-cards creates a new card PUT https://.../accounts/123/credit-cards/456 edits the given card DELETE https://.../accounts/123/credit-cards/456 deletes the given card Decoupling In order to increase resilience and encourage new developments, REST has a strong emphasis on client/server decoupling. This allows both parties to evolve without enforcing a strong-binding contract. To make this work, our API follows some practices and encourages clients to do the same: be liberal in what you accept (see the Format section). avoid hardcoding URIs in your application (see the HATEOAS section)