I'd prefer a "push" to a "pull". A pull requires an API that needs to be secured and supported (this would also introduce a new attack vector). Will need to give it some thought. Very few clubs have expressed any interest though.

Agree with more API access to the data in I/O. I am continuously extracting data from I/O and it is labour intensive to have to hit the download button every time. Running a time triggered job to access I/O data via an API (we use Google Apps Script) would automate much of this effort and provide us with more timely and accurate data of our curling community. Thank you. Ron Pelkey (Calgary Curling Club)