Your own Garmin app

By default every athlete you link registers with Stridee's Garmin app. We can instead register a Garmin app for you, in your name, and run your integration through it: athletes you link from then on register with your app. Garmin's consent screen names you, Garmin's limits are your app's, and nothing about the integration changes: the same POST /v1/connect, the same events, the same GET /v1/activities and GET /v1/wellness.

Getting one#

Email us. We register the app with Garmin for you, hold its credentials, configure its endpoints and check it with a test connection. You have nothing to set up and no Garmin credentials to store.

Once it is live, Providers → Garmin in the console shows that your athletes connect through your own Garmin app. The test connection appears under Accounts as the user stridee-app-check, and you can disconnect it.

What changes for your athletes#

• No Stridee consent page. connect_url goes straight to Garmin. Your athlete agrees to your app, under your terms, on Garmin's own screen. Make sure your privacy policy names Stridee as the processor that receives the data.
• Athletes already connected stay on Stridee's app. An athlete moves to yours by connecting again with a fresh POST /v1/connect. Their connection id stays the same, and anything you already hold for them is not delivered a second time.
• Disconnecting always deregisters at Garmin. The registration is yours alone, so DELETE /v1/connections/{id} ends it at Garmin as well as here.

What your app's APIs decide#

Garmin approves each app for a set of APIs, and only lets an athlete grant what the app is approved for. Every push and backfill already checks what the athlete granted, so an API your app doesn't have is simply off for athletes on it:

Your webhook subscriptions are left as they are, because they cover every provider.