Concurrent tournaments

Looks like there is no support for concurrent tournaments, like the Scottish Open and ISCO happening this weekend. It would be great to pass in an event ID rather than just assuming “next tournament”. That would go for pre-tournament predictions and live stats.

Anyone have the answer?

There is full support for the ISCO and all opposite-tour events. They are under the “opp” tour code plastered all over the home page, banner, and API.

1 Like

Thanks @matt_courchene

The problem @matt_courchene is in the API - the get-schedule endpoint returns both Scottish and ISCO as pga events. I would expect that ISCO would be returned with tour=opp from get-schedule.

The schedule feed has an event_id field, and so do the field endpoints in a given week. So those can be merged and you can determined which event is considered “opp”.

I can handle that logic, but what about live-tournament-stats? no params for tour or event_id for that endpoint

event_id is never a query parameter in current week requests, events are unique by tour.

It’s not in the documentation I guess, but tour=opp will return data. If you try it now you’ll get the Myrtle Beach event which was the last opposite-field event played.

heck yes - hidden nugget. That will work - thanks!