Skip to content
WearLink

Product

IntegrationsData typesUse casesNutrition APIProvider statusSecurityPricing

Developers

DocumentationWebhook eventsAPI referenceSystem status

Resources

GuidesCompareAboutContact
Sign inStart free

Cloud OAuth

Suunto API integration

Provider onboardingThe adapter is implemented; the production OAuth application is awaiting provider approval.OAuth application pending

Connect Suunto freeSee the code
Suunto device illustration

Suunto is an outdoor and dive-focused brand whose cloud API centres on workout files. For mountaineering, trail and diving products it covers device categories nobody else in this list reaches.

The API is straightforward OAuth 2.0, and the main integration cost is in the workout file formats — Suunto exposes rich multi-sport sessions whose structure varies by activity type. Normalising a dive log and a trail run into one workout object requires decisions about which fields are universal and which are activity-specific.

WearLink keeps the universal fields in the shared workout schema and preserves activity-specific detail in the raw payload so nothing is lost.

Connect a Suunto user

Two calls. The first mints a hosted connect URL for your end-user; the second reads the normalised summaries once they have authorised with Suunto. Subscribe a webhook to receive the same objects as they land.

connect + read — suunto
# 1. Create a connect session for your end-user
#    The API key goes in X-WearLink-API-Key, not in Authorization.
curl -X POST https://wearlink.io/api/v1/connections/session \
  -H "X-WearLink-API-Key: $WEARLINK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"user_id": "'"$USER_ID"'", "provider": "suunto", "redirect_uri": "https://yourapp.com/connected"}'

# → { "connect_url": "https://wearlink.io/widget/connect?token=...", "expires_in": 3600 }
# Redirect the user there; they authorise suunto and land back on your redirect_uri.
# The token is scoped to that one user — it is safe to put in a browser URL.

# 2. Pull normalised data whenever you want
curl -H "X-WearLink-API-Key: $WEARLINK_API_KEY" \
  "https://wearlink.io/api/v1/users/$USER_ID/summaries?provider=suunto&days=7"

Suunto data available through WearLink

  • Workouts
  • Heart rate
  • HRV
  • Steps
  • SpO2
  • Stress & recovery
  • Sleep

Webhook events you can subscribe to

  • workout.created
  • heart_rate.created
  • sleep.created
  • recovery_score.created

Normalised families this provider feeds: Sleep, Heart Rate, Workouts, VO2 Max & Fitness Metrics.

What makes the Suunto API hard to integrate directly

These are the things that turn an estimated one-week integration into a one-month one.

Workout shape varies by sport

A dive, a ski tour and a run do not carry the same fields. Code that assumes a fixed workout schema breaks on the first multisport user.

Smaller ecosystem, thinner docs

Fewer developers means fewer worked examples and slower answers when something is ambiguous.

Device sync is the real latency

Data reaches the cloud when the watch syncs to the phone, which for a multi-day expedition user might be days after the activity.

FAQ

Suunto API — frequently asked questions

Does Suunto support dive data?
Suunto's cloud carries dive logs for dive-capable devices. WearLink normalises the common workout fields and preserves the activity-specific detail alongside them.
Is Suunto live on WearLink?
The adapter is implemented; the OAuth application is in onboarding. /providers reflects the runtime state.
How current is Suunto data?
It depends entirely on when the user last synced their watch. Expect gaps for users who are off-grid.

Related

Other cloud integrations

Oura Ring API

Connectable now

The Oura Ring API (v2) is one of the cleaner wearable APIs to work with — the documentation is accurate and the daily-summary endpoints are stable. The complexity is not in reading it, it is in keeping it read: Oura backfills and revises data after the fact, so a sleep record you fetched this morning can legitimately change by this evening.

WHOOP API

Connectable now

WHOOP's developer API exposes the four objects the product is built around — cycles, recovery, sleep and workouts. The data is high quality and the model is coherent, which makes WHOOP a favourite for recovery and readiness products.

Fitbit API

Connectable now

Fitbit has the largest installed base of any dedicated wearable, which makes it the provider most consumer health products need first. It is also the API with the most historical baggage — the surface has accreted since 2011 and it shows in inconsistent date handling and endpoint shapes.

Strava API

Connectable now

Strava is the best-instrumented activity API in the consumer space and the only provider in the WearLink catalogue with a true push model — an activity upload triggers a webhook within seconds, not on a poll cycle. If your product cares about workouts rather than sleep or recovery, Strava is usually the fastest path to a working demo.

Withings API

Connectable now

Withings is the connected-scale and blood-pressure provider, which makes it the one that matters most for clinical-adjacent products — weight management, hypertension programmes, GLP-1 follow-up and remote patient monitoring. Its data is measurement-shaped rather than continuous: discrete readings taken when a user steps on a scale or straps on a cuff.

Garmin API

Provider onboarding

Garmin has the broadest data surface of any provider in the catalogue — if a metric exists in consumer wearables, a Garmin device probably measures it. For endurance, military, occupational-health and research use cases it is frequently non-negotiable.

Start with Suunto — free for up to 3 users

No credit card. Your API key is issued at sign-up, and the hosted connect flow works from the first request.

Start freeRead the docs