I use Sport Ngin as the example only because I know they have a (private) API and they have invested a ton of money, time and effort partnering with USA Hockey to push their service onto all of USAH -- and it's had some success -- I think there's only 1 or 2 Hockey league or team sites that are not on Sport Ngin. 3 Years ago, nobody was on Sport Ngin, so they're growing fast...

The one integration I can think of, today, that is urgent, is the scheduling...

It would be fantastic to connect HWR to Ngin and tell it during setup, that

"League X on HWR is this Ngin id/token/whatever"
"Team Y on HWR is this Ngin id/token/whatever"

And then set individual rules for each, so, for League X, rules might be:

Whenever a game is ADDED to the Ngin schedule, also add it to the HWR schedule.

Whenever a game date is modified on Ngin, etc. etc.

Basic CRUD and how to handle each situation on HWR.

There is no need to send HWR data back to Ngin, I don't think...

Use case for this:

In just one of the leagues we assign, it's roughly a 2,000 game season and we've had over 800 game changes thus far... Last year it was similar amount and we put in a lot of barriers to not make changes easy and they still happen.

So I'm dying for this feature.

If you need help getting access to, or documentation for the Ngin API, let me know, I may be able to help there.

If you prefer NOT to pick a third-party to integrate with you could just expose a HWR API for the master schedule aspect and let people either build their own connection or pay someone to build them for them.

I, personally, would prefer you just expose a scheduling API so I could make all the connections I need to automate as much of the work around the schedule (not assigning) as possible... It's a huge and very real cost to us.

Thanks.