Device IntegrationHealthcare Interoperability

Suunto API Integration Guide 2026: Partner Access

June 20, 202615 min read
Written by
Jitendra Choudhary
Jitendra Choudhary

CTO & Co-Founder

CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Suunto API Integration Guide 2026: Partner Access

You can integrate Suunto watch data through the Suunto API, called the Suunto Cloud API, which runs on Suunto's APIZone portal and is open to organizations through a partner program. Suunto says accepted applicants hear back within two weeks. You get workouts as FIT files with full samples, a webhook when a new workout lands, daily steps and calories, and 24/7 samples for heart rate, SpO2, HRV, sleep and recovery. No API price is published. Suunto's FAQ still says sleep is not available, but the 24/7 Data API on the same portal now serves it. Weight and heart rate zones are still not shared.

Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.

Suunto integration at a glance

QuestionShort answer
Official API?Yes. The Suunto Cloud API on APIZone (apizone.suunto.com), through the partner program.
Cost to developer?Not published on the FAQ. A 2019 launch article said access was free. That is old and unconfirmed today.
Does the end user need a subscription or device?A Suunto watch synced through the Suunto App. Suunto's pages we read mention no paid user subscription.
Same-day start?No. You apply first. Suunto says accepted applicants hear back within two weeks.
Who approves scale-up?Suunto. The developer tier is rate-limited. The Developer API product page sets 10 calls a minute and 200 calls a week. To go live you subscribe to the Production API, which Suunto approves.
HIPAA / BAA?Not published.
Raw vs summary data?FIT files with samples, laps, GPS and heart rate. Workout JSON is summary only. Daily activity is summary.
First buildAbout 5 to 6 weeks including up to 2 weeks of vendor approval. This is our estimate.

Integration strategies

RouteOwn mobile app?Own server?Vendor approval or contract?SDK?Data latencySupported dataNot supportedBest for
Suunto Cloud API (REST)NoYesYes, partner application and API agreementNoPull, on your scheduleWorkouts (JSON summary, FIT detail), daily steps and calories, 24/7 activity, sleep and recovery samples, points of interest, push routes (GPX) and workouts (FIT) to the userWeight, HR zonesAny organization building on Suunto data
WebhooksNoYesPart of the Cloud APINoOn new workout, new route, and new 24/7 activity, sleep or recovery data. Exact delay not publishedJSON body with the workout summary or the 24/7 samples, signed with HMAC SHA-256Weight, HR zonesWorkout-driven products
Phone SDKNone. Suunto's FAQ says "There is no mobile SDK".
SuuntoPlus sports apps (on the watch)NoOptionalFree to build. Publishing needs the partner program and API agreementSuuntoPlus toolsOn the watchCustom on-watch logicNot a data export routeGuided sessions or tests run on the watch
Movescount APILegacy and not compatible with the Cloud API, per the FAQ. Do not start here.
Apple Health / HealthKitYesOptionalNoHealthKitNot publishedWorkouts. Suunto has no official article. Users on the Suunto forum say sleep, VO2 max, routes and sometimes steps are not written.Not publishedTest before you plan on it
Health ConnectNot published.
Aggregators, checked 10 November 2026Terra lists Suunto as a cloud source but says Suunto developer applications are closed. Thryve lists it as a cloud source. Junction lists it as planned only. ROOK does not list it. Spike lists it with no route stated. Validic and Sahha coverage is not published. Open Wearables also documents Suunto.
File export by userNot published.

For a healthcare buyer such as an exercise rehab or sports medicine program: use the Cloud API with webhooks and FIT parsing. It gives you sample-level heart rate during workouts, which is the useful part for supervised exercise. The 24/7 API adds nightly sleep stages and overnight HRV, so check those fields before you add a second source for sleep. For a clinical study, first get written answers on medical use and a BAA, since Suunto publishes neither. For a consumer fitness or coaching app: the Cloud API is the only real route, and route and workout push to the watch lets coaches send sessions back to the athlete.

Build it yourself, use an aggregator, or work with a partner

QuestionBuild in-houseWearable aggregatorBuild with a partner (Nirmitee)
Whose Suunto API app?Yours. One app per account.Depends on the aggregator. Terra says Suunto developer applications are closed.Yours. Suunto asks the client company to apply and list the developers, so we build in your account.
Agreement riskYour counsel reads the API agreementNot published. The agreement is shared only during the application.Your counsel reads it. We design storage around the answer.
Webhooks and token renewalYou build and run them, including the HMAC check and the 2-second replyThe aggregator runs themWe build them, then hand them to you or run them
Data modelSuunto's JSON and FIT filesThe aggregator's schemaFHIR Observations for your EHR or remote monitoring stack
Other devices laterOne new build per deviceMany devices through one APISame pattern reused across devices
Time to first real userDepends on your team, plus up to 2 weeks for Suunto's replyDepends on the aggregator's onboardingAbout 5 to 6 weeks in our estimate, including up to 2 weeks of vendor approval
Cost shapeEngineering timeAggregator fee. Pricing for Suunto on these platforms is not published.Project fee, scoped after a call
Every way to get Suunto data, and what each one needs.

What data you can get

Data typeGranularityHistory windowPush or pull
Workout summary (JSON)Per workout summaryNot publishedPull, after a webhook tells you a workout exists
Workout detail (FIT)Samples, laps, summary, GPS, heart rateNot publishedPull
Daily activity: stepsDaily totals, or 24/7 samplesNot published. 28 days per requestPull, or the 24/7 activity webhook
Daily activity: caloriesDaily totals, or 24/7 samples, in joulesNot published. 28 days per requestPull, or the 24/7 activity webhook
24/7 heart rate, SpO2, HRVSamples. Interval not publishedNot published. 28 days per requestPull, or the 24/7 activity webhook
SleepOne record per sleep segmentNot published. 28 days per requestPull, or the 24/7 sleep webhook
Recovery (body resources, stress state)SamplesNot published. 28 days per requestPull, or the 24/7 recovery webhook
Routes (GPX)Route fileNot applicablePush from you to the user's Suunto account
Planned workouts (FIT)Workout fileNot applicablePush from you to the user's Suunto account

What is inside one Suunto sleep record

The 24/7 sleep endpoint returns one record per sleep segment. These fields come from the API's sleep schema.

FieldWhat it holds
DeepSleepDuration, LightSleepDuration, REMSleepDurationTime in each stage, in seconds
DurationSleep duration in seconds. Suunto notes it also contains awake time in the Gomore algorithm.
BedtimeStart, BedtimeEndBed start and end times in ISO 8601
HRAvg, HRMinAverage and minimum heart rate, beats per minute
AvgHRV, AvgHRVSampleCountAverage HRV in milliseconds for the segment, and how many HRV samples it used
MaxSpo2Maximum oxygen saturation, as a value from 0 to 1
SleepOnsetLatencyDuration, WakeAfterSleepOnsetDuration, WakeBeforeOffBedDurationTime to fall asleep, time awake during the night, and time awake before getting up, in seconds
SleepQualityScore, Feeling, IsNapScore from 0 to 100, the user's own rating from 1 (poor) to 5 (excellent), and whether the segment is a nap

The 24/7 activity samples carry heart rate, minimum and maximum heart rate, step count, energy in joules, SpO2 from 0 to 1, altitude and HRV in milliseconds. Recovery samples carry Balance, the body's energy level from 0 to 1, and StressState: relaxing, active, passive or stressful. The interval between samples is not published.

What you cannot get

  • A minute-by-minute sleep stage timeline. The sleep API gives deep, light and REM totals per sleep segment.
  • Personal data such as weight.
  • Heart rate zones.
  • The HRV method. The spec gives HRV in milliseconds but does not say which HRV measure it is.
  • A mobile SDK.
  • Access for personal projects. The program is for organizations only.
  • More than one app per account.

How to get access

  1. Open the partner program application on suunto.com.
  2. Pick the topic "Suunto Cloud API".
  3. List every developer who needs access. Each one is invited to APIZone. Use one email per account.
  4. Sign the API agreement. It is required.
  5. Wait. Suunto says accepted applicants hear back within two weeks. Who reviews is not published.
  6. In APIZone, get your OAuth client ID and secret and your subscription key. One app per account.
  7. The Developer API allows 10 calls a minute and up to 200 calls a week. When you are ready, subscribe to the Production API. Once Suunto accepts it, your app is shown in the Suunto App.
  8. For partner watch deals, Suunto lists partners@suunto.com.

From zero to your first Suunto data in four steps

  1. Subscribe and configure. Once your company is accepted, subscribe to the Developer API in APIZone and copy a subscription key from your profile. In the OAuth settings, set the app name, client secret and redirect URI. The client ID is created for you.
  2. Connect a test user. Create an account in the Suunto App and sync a watch, or track a workout with the app. Send the user to https://cloudapi-oauth.suunto.com/oauth/authorize?response_type=code&client_id=<CLIENT_ID>&redirect_uri=<REDIRECT_URI>, then swap the code for tokens on your server.
    curl https://cloudapi-oauth.suunto.com/oauth/token \
      --user <CLIENT_ID>:<CLIENT_SECRET> \
      -d grant_type=authorization_code \
      -d redirect_uri=<REDIRECT_URI> \
      -d code=<AUTHORIZATION_CODE>
    The JWT access token has a user claim with the Suunto username. Save it, because webhooks name the user that way.
  3. Make your first call. Every data call sends both the token and the subscription key.
    curl 'https://cloudapi.suunto.com/v3/workouts?since=1709251200000&until=1711929600000&limit=10&offset=0' \
      -H 'Authorization: Bearer <JWT_TOKEN>' \
      -H 'Ocp-Apim-Subscription-Key: <SUBSCRIPTION_KEY>'
    Then fetch /v3/workouts/<workoutKey>/fit for full detail, or /247samples/sleep with from and to in epoch milliseconds.
  4. Turn on webhooks, then go live. Set the notification URL and a notification secret in your app settings, and check the signature on every request. Development runs on the production system with real data. When you are done, subscribe to the Production API. Once Suunto accepts, your app shows in the Suunto App.

Terms you must know

We did not read the full Suunto API agreement. It is shared during the application. Here is what is public and what to ask.

  • Medical use: not published. A healthcare product should get written permission for clinical use. A wellness product should still confirm.
  • PHI and HIPAA: not published. Once Suunto data sits in a patient record it becomes PHI on your side. Suunto has not said how it handles that.
  • BAA: not published. Ask, and plan for no.
  • Storage and retention: not published. Ask how long you may keep data after a user disconnects.
  • AI training: not published. Ask before you train models on Suunto data.
  • Display and branding: not published. Ask for the brand rules before you design.
  • Data selling: not published. Ask before you share or sell any Suunto data, and get the answer in writing.
  • Termination: not published. Ask for notice period and deletion duties.
  • Competing products: not published. Ask whether the agreement limits products that compete with Suunto's own app.
  • Polling: the FAQ asks you to avoid unnecessary polling. Build on webhooks, with a daily fallback fetch.
  • Who may apply: organizations only. One app per account.

Cost and payment terms

  • API fee: not on the FAQ. A 2019 launch article (sgbonline.com) said Cloud API access was free. That is seven years old. Confirm with Suunto.
  • End users need a Suunto watch and the Suunto App. No paid user subscription is mentioned.
  • Higher rate limits: on request. Any fee for them is not published.
  • Aggregator fees: not published.

Use cases

One Suunto workout from watch to the therapist.

Supervised exercise rehab

The patient links Suunto in your portal with OAuth. After each session Suunto calls your webhook with the username and workout ID. Your server fetches the FIT file, pulls heart rate and duration, and writes FHIR Observations into the EHR so the therapist sees effort per session. Data used: FIT heart rate samples, workout duration.

  • Rate limit hit during a backfill. Fix: queue requests and ask Suunto for higher limits before go-live.
  • Webhook missed during downtime. Fix: run a daily fetch of recent workouts as a safety net.
  • Workout heart rate read as a clinical vital sign. Fix: label it patient-generated activity data in the EHR.

Clinical trial activity endpoint

Participants use Suunto watches. Your server collects daily steps and calories by a scheduled pull, plus workouts by webhook, and stores FIT files as source data. Data used: daily steps, workouts.

  • Daily totals have no webhook of their own. Fix: use the 24/7 activity webhook, or fetch daily totals when a workout arrives plus a daily fallback, as Suunto suggests.
  • Sleep is needed as a secondary endpoint. Fix: use the 24/7 sleep API, and get written approval for clinical use first.
  • History window unknown. Fix: connect each participant at enrollment.

Endurance coaching app

The athlete connects Suunto in your app. Workouts flow in by webhook. Your coach builds a session and you push it as a FIT workout, or push a GPX route, to the athlete's Suunto account. Data used: FIT workouts, GPX routes.

  • Coach wants HR zones from Suunto. Fix: compute zones yourself from the heart rate samples and the athlete's max HR.
  • Workout JSON lacks samples. Fix: always pull the FIT file for detail.

Employer wellness challenge

Employees link Suunto with other brands. You pull daily steps and count workouts per week for a leaderboard. Data used: daily steps, workout summaries.

  • Low developer-tier limits with many users. Fix: request higher limits early and space daily pulls through the day.
  • One app per account. Fix: keep a single production app and use separate accounts for test.

Guided test on the watch

A sports clinic builds a SuuntoPlus sports app that runs a field test on the watch. Whether the test result shows up in the workout data you read through the Cloud API is not published. Confirm with Suunto before you design around it. Data used: workout and FIT data, if the result lands there.

  • You can build without signing up, but you cannot publish without the partner program. Fix: apply at the start.

Suunto data in an EHR or remote monitoring program

Most healthcare teams want Suunto readings next to clinical data, not in a separate app. The usual pattern is to turn each reading into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Get written approval for clinical use first, since Suunto publishes nothing on it.

Suunto valueFHIR ObservationCode
HR in 24/7 samples, avg_heart_rate in FITHeart rate, beats per minuteLOINC 8867-4
SpO2 in 24/7 samples (0 to 1)Oxygen saturation by pulse oximetry. Multiply by 100 for percent.LOINC 2708-6, plus 59408-5 for pulse oximetry
StepCountNumber of stepsLOINC 55423-8
EnergyConsumption (joules)Calories burned. Divide by 4,184 for kilocalories.LOINC 41981-2
Workout total_timer_timeExercise durationLOINC 55411-3
Deep, light and REM sleep durationsDeep, light and REM sleep durationLOINC 93831-6, 93830-8, 93829-0
Sum of deep, light and REMSleep duration. Do not use Duration as is, since it can include awake time.LOINC 93832-4
HRV, SleepQualityScore, Balance, StressStateDevice-specific ObservationYour own code system. Suunto does not say which HRV measure it uses, and the scores are Suunto's own.

Keep the Suunto workout key or the sample timestamp on each Observation, so a repeat webhook does not create a duplicate.

Known blockers and gotchas

  • The FAQ is out of date on sleep. It still says sleep is not available, but the 24/7 Data API serves sleep, HRV and SpO2. Build from the API pages, not the FAQ.
  • Two credentials per call. Calls need a Bearer JWT and the Ocp-Apim-Subscription-Key header. Plan for both from the first call.
  • Tight developer limits. Suunto's Developer API product page sets 10 calls a minute and 200 calls a week. Production limits are not published. Ask Suunto for them.
  • No mobile SDK. Data access runs server to server through the Cloud API. Your phone app only hosts the OAuth link step.
  • Movescount is a dead end. The old API is separate and not compatible.
  • Organizations only. Individual developers cannot get access.
  • SuuntoPlus news. A March 2026 third-party report says Suunto opened SuuntoPlus to all developers. Confirm on apizone.suunto.com/suuntoplus, which still states publishing needs the partner program.

Delivery timeline

Our estimate. Steps marked "vendor" depend on Suunto.

WeekWorkDepends on vendor?
1 to 2Partner application, API agreement, APIZone invitesYes. Suunto says within two weeks
3OAuth flow, JWT exchange, subscription key handlingNo
4 to 5Webhook receiver, FIT parsing, daily activity pullNo
6FHIR mapping and testing with real watchesNo

Questions to ask Suunto before you sign

  1. Is the Cloud API still free, and will that change?
  2. What are the exact rate limits for our tier, and how do we raise them?
  3. Is the 24/7 sleep and recovery data included in our production subscription?
  4. Does the API agreement allow clinical or medical use?
  5. Will you sign a BAA, and where is data stored?
  6. How far back can we fetch history for a new user?
  7. How long does a refresh token last?
  8. How long does the webhook circuit breaker pause sending after failures?

Other device integration guides

Suunto is often one device among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.

Ready to build with Suunto data?

Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. We do not have an existing Suunto partnership. Book a call about your device integration.

For whoever builds this

  • Auth: OAuth 2.0 authorization code flow. Exchange the code for a JWT using Basic auth with client ID and secret. Every call sends Authorization: Bearer <JWT> and Ocp-Apim-Subscription-Key.
  • Tokens: the quick start example returns expires_in 86400 (24 hours), a refresh token and scope workout. Refresh with grant_type=refresh_token. The full scope list and refresh token lifetime are not published. Disconnect a user with GET /oauth/deauthorize.
  • Rate limits: Developer API product, 10 calls per minute and 200 per week (apizone.suunto.com product listing). Production limits not published. 503 means service capacity exceeded.
  • Webhook: JSON POST with a type field (WORKOUT_CREATED, ROUTE_CREATED, SUUNTO_247_ACTIVITY_CREATED, SUUNTO_247_SLEEP_CREATED, SUUNTO_247_RECOVERY_CREATED) and username. Verify X-HMAC-SHA256-Signature with your notification secret. Reply 2xx within 2 seconds. Failed sends retry with exponential backoff, and too many failures trip a circuit breaker that pauses sending. The legacy form post (workoutid, username) still works on a separate URL.
  • Daily activity: /247samples/daily-activity-statistics gives daily totals, /247samples/activity gives samples. Both take at most 28 days per request, and Suunto advises a fetch every 24 hours.
  • FIT holds samples, laps, summary, GPS and heart rate. Workout JSON is summary only.
  • Uploads: GPX for routes, FIT for workouts.
  • FHIR mapping (our mapping, LOINC codes checked 11 Nov 2026): heart rate LOINC 8867-4, steps 55423-8, calories burned 41981-2, exercise duration 55411-3.
  • Versions: the workout API is /v3/workouts. The v2 workout API is marked deprecated, sunset date not published. Movescount API is legacy and separate.

Sources

All read 10 November 2026.

  • Suunto forum, Apple Health thread, https://forum.suunto.com/topic/739/apple-health, read 10 November 2026.
  • Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
  • Junction providers list, https://docs.junction.com/wearables/providers/introduction, read 10 November 2026.
  • Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
  • ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
  • Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
  • Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
  • Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
  • https://apizone.suunto.com/how-to-start, read 11 November 2026.
  • https://apizone.suunto.com/webhooks, read 11 November 2026.
  • https://apizone.suunto.com/fit-description, read 11 November 2026.
  • https://apizone.suunto.com/developer/apis?api-version=2022-04-01-preview (API list, operations, schemas and products), read 11 November 2026.
  • https://apizone.suunto.com/faq
  • https://apizone.suunto.com/apis
  • https://apizone.suunto.com/suuntoplus
  • https://openwearables.io/docs/providers/suunto-api-integration (third party)
  • https://sgbonline.com/suunto-launches-partner-program-to-expand-its-digital-ecosystem/ (third party, 2019)
  • https://the5krunner.com/2026/03/11/suunto-opens-suuntoplus-to-all-developers-a-direct-challenge-to-garmins-connect-iq/ (third party)

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

Does Suunto have a public API?

Yes. The Suunto Cloud API runs on APIZone and is available to organizations through the Suunto partner program. Personal projects are not supported.

How long does Suunto API approval take?

Suunto's FAQ says accepted applicants hear back within two weeks. You apply on suunto.com with the topic Suunto Cloud API and sign the API agreement.

Is the Suunto API free?

The FAQ does not list a price. A 2019 launch article said access was free, but that is old and unconfirmed. Ask Suunto before you budget.

Can I get sleep data from the Suunto API?

Yes, through the 24/7 Data API. It returns deep, light and REM sleep, heart rate, HRV and SpO2 per sleep segment, with a webhook for new sleep data. Suunto's FAQ still says sleep is not available, so build from the API pages. Weight and heart rate zones are not shared.

What data does the Suunto API provide?

Workouts as JSON summaries and FIT files with samples, laps, GPS and heart rate, plus daily steps and calories. You can also push GPX routes and FIT workouts to a user's account.

Does Suunto have webhooks?

Yes. Suunto sends webhooks for new workouts, new routes, and new 24/7 activity, sleep and recovery data. Each one is signed with HMAC SHA-256 using your notification secret. Daily totals have no webhook of their own.

Is there a Suunto mobile SDK?

No. The FAQ says there is no mobile SDK. Data comes through the Cloud API, server to server, after the user links their account with OAuth.

What are the Suunto API rate limits?

The Developer API allows 10 calls a minute and up to 200 calls a week, per Suunto's product listing on APIZone. Production limits are not published. You subscribe to the Production API when you go live.

Can I still use the Movescount API?

Suunto calls Movescount separate and not compatible with the Cloud API. Build on the Cloud API instead.

Will Suunto sign a BAA?

Suunto publishes nothing on HIPAA or BAAs. Ask before using Suunto data in a covered healthcare product.

Do my users need a paid Suunto subscription?

Users need a Suunto watch that syncs through the Suunto App. The Suunto pages we read mention no paid user subscription.

Which Suunto data types have a webhook?

Five: new workout, new route, and new 24/7 activity, sleep and recovery data. The type field in the JSON body tells them apart. The old form post with workoutid and username still works on a separate URL.

How do I verify a Suunto webhook?

Compute an HMAC SHA-256 of the request body with your notification secret and compare it with the X-HMAC-SHA256-Signature header. Reply with a 2xx status within 2 seconds. Failed sends retry with exponential backoff, and too many failures pause sending for your app for a while.

How long does a Suunto access token last?

In Suunto's quick start example the token response has expires_in 86400, which is 24 hours, plus a refresh token. Get a new pair with grant_type=refresh_token. The refresh token lifetime is not published.

How much history can I fetch in one call?

The 24/7 activity, sleep and recovery endpoints take at most 28 days per request, and Suunto advises a fetch every 24 hours. The workout list takes since and until in epoch milliseconds, returns 50 workouts by default, and pages with offset. How far back history goes is not published.

What units does the Suunto API use?

Energy is in joules, not kilocalories. SpO2 is a value from 0 to 1. HRV is in milliseconds and sleep durations are in seconds. The 24/7 endpoints store and return UTC time, and take from and to in epoch milliseconds.

Which Suunto workout API version should I use?

Version 3, at /v3/workouts. The v2 workout API is marked deprecated on APIZone. A sunset date is not published.
Share