@david – two questions that decide a lot for self-hosted users: (1) will the block apply to an athlete’s own personal API key as well, or only to OAuth apps? (2) Activities an athlete uploads themselves (e.g. the original FIT fetched from their own Garmin account, as garmin-intervals-bridge does in its upload mode) are the athlete’s own files, not data delivered through Garmin’s partner API – I’d assume those stay accessible, as do custom wellness fields the athlete writes. Could you confirm?
For reference, the clause behind this seems to be 5.1(o) of the Connect Developer Program Agreement (no “Licensee application programming interface to provide End User Data to third-party … services … not approved by Garmin in writing”). If it comes to that, the garmin-intervals-bridge already has an upload mode (official import off, originals uploaded as the athlete’s own files) – happy to make that the recommended setup.