Crunch Time: Embrace the Cookie Monster Within!

We use cookies to enhance your browsing experience and analyse our traffic. Nothing beyond essential cookies runs until you choose. You can change your mind any time in our Cookie Policy.

  • Unified API
  • Mobile SDK
  • Connection Widget
  • Streaming
  • Lab Reports API
  • Graph API
  • Health Scores
  • Health Rewards
  • Workouts & Routes
  • Predictions
  • Lab Testing
  • DNA Testing
  • AI Interface
  • Enterprise
  • Insurance
  • Integrations
  • Research
  • Podcast
  • Blog
  • Reports
  • Events
  • Documentation
  • Community
  • Example apps
  • Wearable Data
  • About
  • Customers
  • Partners
  • Startup Accelerator
  • Careers
  • Support
  • Pricing
Terra
PricingHLTH '26
Become an integrationGet started
zap

Latest

zap

Popular

API

Unified API

SDK

Phone SDK

Authentication

Widget

Streaming

Streaming

Graph API

Graph API

Wearable data for a running & cycling challenge platform (France) – fit + demo account?

All

AbleMink3 weeks ago

Hi,

I'm Guillaume, founder of Chally, a platform based in the French Alps (Gap) that runs connected sports challenges for running shops, bike shops and sports clubs.

How it works:

  • A shop or club creates monthly challenges: distance (e.g. 120 km of running in November), elevation gain (2,500 m of trail D+), number of sessions (8 runs), or a specific climb/segment.
  • Members connect their account once; their activities are counted automatically.
  • When they complete a challenge, they collect a reward in store (pin, discount) with a QR code.
  • Each shop or club has a community page with a monthly leaderboard and group-ride check-ins.

Today we use the Strava API, but we want to support watches directly (Garmin first, then Coros, Suunto, Polar, Apple Health), and Strava does not allow distance-based leaderboards.

Data we need per activity: sport type (run, trail run, road bike, MTB, gravel), date, distance, elevation gain, duration, and ideally GPS track or start location (to detect a climb). We do not need health data (sleep, heart rate, etc.).

Expected volume:

  • Pilot: 2–5 shops/clubs, 100–500 connected users
  • Year 1: about 20 shops/clubs, 1,000–3,000 users

My questions:

  1. Is your solution a good fit for this use case (activity data only, webhooks when a new activity is synced)?
  2. Which providers are covered today, especially Garmin, Coros, Suunto and Polar? Do we go through your own Garmin partnership?
  3. Can we display rankings by distance/elevation with data coming through you, under each provider's terms?
  4. Pricing at our volume: is there a startup or pilot plan below your standard plan?
  5. GDPR: where is the data hosted, and can you sign a DPA? Our users are in France.
  6. Could we get a sandbox or demo account to test the integration before committing?

Thanks, Guillaume Tourette Chally – connected challenges for shops & clubs Gap, France

terra

Vanessaadmin3 weeks ago

Hi Guillaume,

Yes, Terra fits an activity-only, webhook-driven challenge platform like Chally: your users connect their wearable once through the Terra widget, and each new activity gets pushed to your backend with sport type, date, distance, duration, elevation gain and GPS fields (polyline_map_data.summary_polyline and position_samples with lat/lng/altitude). You can disable the data types you don't need (sleep, body, nutrition) in the Terra dashboard so you only consume activity events.

On the providers you asked about, all four are supported, with different credential models:

  • Garmin is event-driven, but Garmin requires every company that connects Garmin users to have its own developer app on the Garmin developer portal.
  • Polar is event-driven, credentials managed by Terra, so nothing for you to register.
  • Coros is polled on roughly a 15-minute cadence (Coros does not expose webhooks to third parties), credentials managed by Terra.
  • Suunto is event-driven, credentials managed by Terra.
  • Apple Health comes through Terra's iOS SDK on iPhone, with no provider app to register.

The full list, with sync mode and credential type per provider, is at Supported integrations.

For leaderboards by distance or elevation, each provider's own terms apply, and the one worth flagging is Strava: Strava's API terms prohibit third-party apps from displaying a user's activity data to anyone other than the user themselves, which blocks cross-user leaderboards built on Strava-sourced data. Garmin, Polar, Coros, Suunto and Apple Health do not have that restriction, so distance and elevation leaderboards built from those sources are fine. Garmin additionally requires visible attribution ("Garmin [device model]") on any screen that uses Garmin data, which is worth planning into the UI from day one.

On pricing, the Unified API starts on the Quick Start plan, which includes 100,000 credits per month. One active authentication (one connected wearable) costs 200 credits/month, so your pilot (100 to 500 users) sits inside the free allowance. At 3,000 single-source users you would be around 600,000 credits/month, billed at $0.005 per credit beyond the first 100,000 (dropping to $0.003 per credit above 1,000,000). Full breakdown at Pricing. For a tailored pilot or startup discussion, drop your details at tryterra.co/enterprise/contact and the commercial team can take it from there.

GDPR, DPA signing and the current hosting region are commercial conversations rather than a public docs answer. The same contact form is the right place to ask, and the team can share the DPA and confirm hosting and sub-processors against your French user base before you commit.

For the sandbox: every paid Terra account comes with a testing and staging environment that supports up to 50 connected users, with its own dev-id and API key visible in the dashboard header. You can register, flip to Testing, connect a Garmin or Polar account you own, and watch webhook events arrive before you touch production. Details at Understanding Terra environments.

Good luck with the pilot! and happy to see Chally take shape.