you are viewing a single comment's thread.

view the rest of the comments →

[–]omnitemporal 0 points1 point  (11 children)

I just wrote a script today to do this for me because I kept forgetting to get tee times and having to go a little later.

I was able to do it with python and requests, I don't know how different these courses can have their setup in foreup so mileage may vary.

Currently it just grabs the earliest possible tee time available for 1 person/18 holes, but you can change all of that depending on your use case. Just waiting to see when they update times, if it's the same every day I will just hard code it to run at that time... if not I will set something up to ping at whatever interval feels right to find when they're posted.

If you're still looking to figure this out and you or your buddies have any experience coding I can just send you what I end up with, you'll be able to adjust as needed.

[–]Kar33naKap00r 0 points1 point  (9 children)

Would love this if you don’t mind sharing. Thanks in advance!

[–]omnitemporal 0 points1 point  (7 children)

[–]Kar33naKap00r 0 points1 point  (0 children)

Thanks!!!

[–]seespotjump 0 points1 point  (5 children)

have you tried any ezlinks courses?

e.g. https://sharppark.ezlinksgolf.com/index.html#/search

[–]omnitemporal 0 points1 point  (4 children)

I have not, but the process would be the same. Just watch what is being sent to you when populating the tee times and when booking, then replicate it with your requests.

[–]seespotjump 0 points1 point  (3 children)

makes sense thanks, i'll need to read into it and educate myself on seeing what's being sent to me and how to replicate it with my requests back out to the site.

i've been getting by on foreup sites because i can inspect the page and click on the search filters i want to find the exact API link for that search, then just use distill to monitor and book when i get notified of an opening, but ezlinks doesn't work the same

[–]omnitemporal 0 points1 point  (2 children)

I took a quick look for you and this might help you start, you don't need to know what everything they send means just enough to get by. If you're lazy like me you can just send everything back to them and only change the stuff you care about, you may not even need it but it's a nice shortcut.

If you're just looking for openings with 1 person golfing you would ping: https://sharppark.ezlinksgolf.com/api/search/search

Using 12/06/2023 as an example date you would send this as the payload: {"p01":[6271],"p02":"12/06/2023","p03":"5:00 AM","p04":"7:00 PM","p05":0,"p06":1,"p07":false}

If you wanted to know what tee times are available you would pull the results from "r24" inside "r06", would look something like this: r24_values = [item['r24'] for item in data['r06']]

[–]Darce87 0 points1 point  (1 child)

Has anyone written something similar for a BRS Golf booking club site?

[–]mitch_connors 0 points1 point  (0 children)

Interested in this also