Data Retrieval From Dynamic Odds
Budget: $250 – $750 AUD
I am a Bookmaker in Queensland and I have a Computer System for Bookmakers use. I currently get a data feed from Dynamic Odds (https://www.dynamicodds.com) as to Race Fields, Dividend changes, Results etc associated with Betting.
Dynamic Odds have recently updated their website and use Graphql.
I have a program that currently extracts their old data and presents it to me as an XML file. Ideally, I would like the new program to present me with a file in the same format as the existing Program.
I require a windows console desktop app to access a website with a Graphql API and writes the returned data as XML files.
The resulting program will be called by an existing “third party” application by passing command line arguments to this console application which then processes the created XML files. The definition of the calling parameters and the required XML will be provided.
A Graphql 'playground' will be provided. The documentation for the queries and the schema is provided in the 'playground'.
For ease of use, the graphql testing environment has dummy credentials. OAUTH will be required for production. Details on how the application should obtain an access token to use with the API will be provided.
The development language is free to choose although .NET or Java would be preferred. No scripting languages.
The code needs to be well documented.
Dynamic Odds have recently updated their website and use Graphql.
I have a program that currently extracts their old data and presents it to me as an XML file. Ideally, I would like the new program to present me with a file in the same format as the existing Program.
I require a windows console desktop app to access a website with a Graphql API and writes the returned data as XML files.
The resulting program will be called by an existing “third party” application by passing command line arguments to this console application which then processes the created XML files. The definition of the calling parameters and the required XML will be provided.
A Graphql 'playground' will be provided. The documentation for the queries and the schema is provided in the 'playground'.
For ease of use, the graphql testing environment has dummy credentials. OAUTH will be required for production. Details on how the application should obtain an access token to use with the API will be provided.
The development language is free to choose although .NET or Java would be preferred. No scripting languages.
The code needs to be well documented.
Related categories:
GraphQL