nishaldesai
commented
3 months ago Last known communication with the CTO at the time, June 2021:
Status There are two GoodGym open data feeds:
- an "old" feed: https://www.goodgym.org/api/happenings
- a "new" feed: https://www.goodgym.org/api/openactive/events
The reason for the new feed is that Patrick [then technical liaison] did some work to upgrade the Goodgym data feeds to be more conformant to the current OpenActive (OA) standards. It also has more data in it (the old feed did not include Community Missions, for example). He completed this work and shared with us directly the new feed URL.
There is also a booking endpoint, at http://www.goodgym.org/api/external_registrations, which is designed to work with the old feed to take direct bookings from third party applications.
Where we had got to We (imin) and several other organisations in the OpenActive ecosystem have integrated with the old feed.
Patrick released the new feed, and we were in the process of testing it, when COVID hit. Everything paused at that point.
It looks like https://www.goodgym.org/api/happenings still resolves, but https://www.goodgym.org/api/openactive/events does not fetch any data. However, https://www.goodgym.org/api/happenings does not provide a proper next URL and the validator catches lots of issues.
Conclusion: feed is not usable.
Suggested next steps:
- engage Goodgym to find out the status of https://www.goodgym.org/api/happenings and if it can easily be reinstated.
- once live, check against the validator to confirm usability
Development Progress Tracker
This issue aims to provide public visibility of this new OpenActive implementation's development progress. The task list below tracks high level progress at-a-glance, while comments on this issue are used to provide updates in more detail.
Speculative
In Development
In Review
Certified and Live