API would be a great addition!
If they want to grow, they would allow course API downloads and people would create incredible new ways to see the data (your +/- to par based on hole distance; you vs world in rank order of how difficult each hole is–-which would need all that data about each hole’s global average; mapping of course +/- to par color coded by which tee and which basket is used; etc, etc). An isolationist philosophy of hoarding all the info and never doing anything with it because of lack of programmers is never a good idea.
Use case for API - filtering my list of played courses by what state they are in. Currently I would have to export my scorecard history then run a script to search for each course name on Udisc & scrape the page to access data about the course eg location.
1 Like
@shandrow download is possible. I have a python script that will grab these each week on a timer and import into our scoring db if you are interested.
i will literally stand up a public java api with ratelimiting, apikeys, RLS, loadbalancing, containerized, least privileges, before most people start the 2026 season, pro bono
just give read only access and we’re good
i want an api so i can create a dashboard of my data displayed with a magic mirror
i second the notion about this not being udisc’s #1 priority as bizarre
edit: yes this is the only reason i got on the forums
1 Like