Develop OWN Indian Horse Racing Odds API
Budget: ₹12,500 – ₹37,500 INR
I want to expose my own Indian horse-racing prices—win, place, second-win and third-win—through a clean, need own API secure REST API. The system has to let me enter or edit odds manually and then publish them in real time, together with live race results and basic horse information, to any application that calls the API.
The job covers:
• Building the underlying data model for meetings, races, runners and the four price types.
• An admin interface (web or CLI) where I can key the odds and mark results as they come in.
• REST endpoints that return JSON: current betting odds, race results and horse details, all refreshable immediately after I hit save.
• Real-time delivery—WebSockets, Server-Sent Events or another push mechanism—so client apps don’t have to poll.
• Simple token or key-based authentication and concise developer documentation that includes sample requests, response schemas and error codes.
I’ll consider the project complete when I can:
1) input or adjust odds for any active Indian race,
2) see those changes reflected through the API within a couple of seconds, and
3) retrieve accurate results and runner data the same way.
Use any modern stack you’re comfortable with, as long as updates stay lightning-fast and the code is well organised for future maintenance.
The job covers:
• Building the underlying data model for meetings, races, runners and the four price types.
• An admin interface (web or CLI) where I can key the odds and mark results as they come in.
• REST endpoints that return JSON: current betting odds, race results and horse details, all refreshable immediately after I hit save.
• Real-time delivery—WebSockets, Server-Sent Events or another push mechanism—so client apps don’t have to poll.
• Simple token or key-based authentication and concise developer documentation that includes sample requests, response schemas and error codes.
I’ll consider the project complete when I can:
1) input or adjust odds for any active Indian race,
2) see those changes reflected through the API within a couple of seconds, and
3) retrieve accurate results and runner data the same way.
Use any modern stack you’re comfortable with, as long as updates stay lightning-fast and the code is well organised for future maintenance.