Strava API Integration Guide 2026: Access, Data, Limits
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.

The Strava API is the official way to integrate Strava: you connect through its API v3. It uses OAuth sign-in and webhooks, and access is free today. You can start with your own account the same day, but the developer who creates the app needs a Strava subscription, and anything past 10 connected athletes needs Strava's review. The rule that decides most projects sits in the Strava API Policy, effective June 1, 2026: you may keep Strava data in a cache for no more than seven days, you may not combine it with other customer data, and you may not use it with any AI application. Read that section before you plan a clinical record, a care-team dashboard or an AI coach on top of Strava.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.
Strava integration at a glance
| Question | Short answer |
|---|---|
| Is there an official API? | Yes. Strava API v3, REST, OAuth 2.0, with webhooks for activity events. |
| Cost to the developer | No API fee today. The API Agreement (section 3.2) says access is "currently provided at no charge" and Strava may charge later with notice. The developer docs say a Strava subscription is required to create an app. |
| Does the end user need anything paid? | A Strava account. The API Policy (section 3.3) says Standard Tier apps are subject to subscription requirements, "including a requirement that the developer or specified end users maintain an active Strava subscription". The exact current requirement for end users is not published on the pages we read. |
| Same-day start? | Yes, for your own data ("Single Player Mode", 1 athlete). You can self-upgrade to 10 athletes from the API settings page. |
| Who approves scale-up? | Strava, through the Developer Program form. No review time is promised (Policy 3.6). The Extended Access Tier is "generally inclusive" of apps with 10,000 users or more that Strava approves (Policy 3.3). |
| HIPAA and BAA | Neither the Agreement nor the Policy mentions HIPAA, a BAA or medical use. The Agreement (14.6) treats you and Strava as independent data controllers. |
| Raw or summary data? | Both for workouts. Activity summaries plus per-second style streams (time, distance, GPS, altitude, speed, heart rate, cadence, power, temperature). No sleep, HRV, SpO2 or glucose. |
| Storage | Cache only, up to seven days (Policy 6.2). No persistent index or bulk corpus (Policy 5.5). |
| Aggregators and AI | Banned as described in Policy 5.16 (intermediaries and aggregators that re-expose the API) and Policy 5.3 (any AI application). |
| First build | About 2 weeks for OAuth, webhooks and activity sync, then a Strava review with no published wait. Our estimate. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Cloud REST API (v3) | No. A web app works. | Yes, for OAuth tokens and calls. | Click-through API Agreement. Strava review past 10 athletes. | No. Plain HTTPS. Strava may offer open-source libraries (Agreement 9.4). | Not published. You fetch after the webhook event arrives. | Athlete profile, activities, laps, streams, zones, gear, clubs, routes, segments. | Sleep, HRV, SpO2, glucose, ECG, all-day steps. Other users' data. | Any product that shows athletes their own workouts. |
| Webhooks (push) | No | Yes. A public HTTPS callback that answers within 2 seconds. | Same as REST. One subscription per app. | No | Event arrives soon after the activity changes. You then fetch the data. | Events only: activity create, update, delete, and athlete deauthorization. | The activity data itself. The event carries IDs, not the workout. | Avoiding polling and meeting the 48-hour deletion rule. |
| Phone SDK | n/a | n/a | n/a | No Strava health SDK found in the docs we read. | n/a | n/a | n/a | n/a |
| Apple Health (HealthKit) | Yes, iOS | Yes, to upload | No Strava approval. Apple review of your app. | HealthKit | When the phone syncs | Strava activities, when the user turns on Send to Health | Routes from Garmin or Zwift activities are not sent | Teams that already read HealthKit for other devices |
| Health Connect (Android) | Yes, Android | Yes, to upload | No Strava approval. Google Play health permission review. | Health Connect | When the phone syncs | Duration, distance and calories of GPS-recorded activities | Everything else, including heart rate and routes | Simple activity totals on Android |
| Partner or enterprise API | No | Yes | Extended Access Tier, admitted case by case (Policy 3.3). An allowlist exists for restricted endpoints (Policy 3.2). | No | Same as REST | Same API, more athletes and higher limits. | No separate health data product found. | Apps expecting 10,000 or more users. |
| Aggregators, checked 10 November 2026 | Terra, Junction and Thryve still list Strava as a cloud source, and Junction asks you to bring your own Strava OAuth app. ROOK does not list it. Strava API Policy section 5.16 bars abstraction layers, integration platforms and pass-through proxies, and section 5.3 bars use in any AI application. Not recommended unless the aggregator shows you written permission from Strava. | |||||||
| File export (user's Bulk Data Export) | No | Yes, to parse uploads | No. Policy 6.6 says each user may export their own data free. | No | Manual, whenever the user exports | The user's own archive, as Strava exports it. | Ongoing sync. File contents not documented in the sources we read. | One-off history for a study or intake. |
For a wellness or coaching app that shows athletes their own training, use the REST API plus webhooks. Apply for the Developer Program early, because the review has no set time. For a healthcare program, plan Strava as a patient-facing feature only, and ask Strava in writing before you store data in a clinical record, show it to a clinician, or combine it with other health data. Policies 5.4, 5.5 and 6.2 read as blocking all three.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose Strava API app? | Yours | Depends on the aggregator. Junction asks you to bring your own Strava OAuth app. | Yours. We build it in your account. |
| Aggregator clause risk | Low, if you keep one app per product | Highest. Policy 5.16 bars aggregators and pass-through proxies that re-expose the API. | Low. The app stays yours and is not shared across services. |
| Webhooks and token renewal | You build and run them | The aggregator runs them | We build them, then hand them to you or run them |
| Data model | Strava's own fields | The aggregator's schema | FHIR Observations, if Strava confirms you may store the data |
| Other devices later | One new build per device | Many devices through one API | Same pattern reused across devices |
| Time to first real user | Same day for your own account | Depends on the aggregator's onboarding | About 2 weeks of build in our estimate, plus Strava review past 10 athletes |
| Cost shape | Engineering time and a Strava subscription for the developer | Aggregator fee. Pricing for Strava on these platforms is not published. | Project fee, scoped after a call |
What data you can get
| Data type | Granularity | Scope needed | History window | Push or pull |
|---|---|---|---|---|
| Athlete profile (name, weight, FTP, clubs, bikes, shoes) | Current values | read, profile:read_all | Current only | Pull |
| Activity summary (type, start time, distance, moving and elapsed time, elevation, average and max heart rate, calories, kilojoules for rides, power) | One record per activity | activity:read (activity:read_all for "Only You" activities) | Not published | Webhook event, then pull |
| Activity streams: time, distance, latlng (GPS), altitude, velocity_smooth, heartrate, cadence, watts, temp, moving, grade_smooth | Sample by sample, as recorded | activity:read or read_all | Not published | Pull |
| Laps | Per lap | activity:read | Not published | Pull |
| Heart rate and power zones | Per activity, and athlete zone settings | activity:read, profile:read_all | Not published | Pull |
| Athlete stats (totals) | Rolled-up totals | read | Not published | Pull |
| Gear, clubs, routes (GPX and TCX export), segments and segment efforts | Per object | read, read_all | Not published | Pull |
| Write: create activity, upload file, update athlete weight and FTP | Per call | activity:write, profile:write | n/a | Push to Strava |
Heart rate appears only when the athlete recorded it with a sensor. Check has_heartrate before you ask for the stream. Latency from workout to API is not published.
What is inside one Strava activity
GET /activities/{id} returns the detailed record. These fields and units come from the API reference.
| Field | What it holds |
|---|---|
| sport_type | The activity type. The older type field is marked deprecated, so read sport_type. |
| start_date, start_date_local, timezone | Start time in UTC, start time in local time, and the time zone |
| distance, moving_time, elapsed_time | Meters and seconds. Moving time leaves out stops. |
| average_speed, max_speed | Meters per second |
| calories | Kilocalories for the activity |
| average_watts, weighted_average_watts, device_watts | Rides only. device_watts is false when power is estimated, not measured by a power meter. |
| manual, trainer, device_name | Whether the athlete typed it in, whether it was on a training machine, and the recording device |
| laps, splits_metric, best_efforts | Per lap data, per kilometer splits for runs, and best efforts |
Streams give the raw series. Heart rate is in beats per minute, cadence in rotations per minute, power in watts, temperature in degrees Celsius, altitude and distance in meters, and grade in percent. Each stream also reports original_size, the number of data points, and a resolution of low, medium or high. Strava does not publish a fixed sample rate, so read the time stream alongside each series.
What you cannot get
- Sleep, sleep stages, HRV, resting heart rate trends, SpO2, skin temperature, blood pressure, glucose or ECG. Strava has no endpoints for these in the docs we read.
- All-day steps or daily activity outside recorded workouts.
- Data about anyone other than the signed-in athlete. Policy 2.3 limits display to that user, even for public data.
- Activities the athlete hid with "Only You", unless they grant activity:read_all.
- A long-term copy. Policy 6.2 caps your cache at seven days.
- Any use of the data in an AI application, including putting it into a model's context window (Policy 5.3).
- Bulk, de-identified or aggregate datasets for analytics, even with consent (Policies 5.4, 5.5, 5.10).
- A server-to-server feed without each athlete's OAuth consent.
How to get access
- Sign up for Strava and hold a Strava subscription. The getting-started guide says "A Strava subscription is required" to create an app.
- Create an app at strava.com/settings/api. It starts in Single Player Mode with athlete capacity 1. Same day.
- Upgrade to athlete capacity 10 from the API Settings Dashboard. Self-service, same day.
- Build to the Brand Guidelines, including the "Connect with Strava" button.
- Submit the Developer Program form with screenshots of every place Strava data appears and the Connect button. Strava approves. Policy 3.6 says there is no fixed review time and "you will hear from Strava if you are admitted". Increased access "is not a guarantee".
- Ask for higher rate limits only once you are near capacity. Strava says it raises limits only for apps approaching capacity.
- For 10,000 users or more, apply for the Extended Access Tier. Case by case. No published wait.
From zero to your first Strava data in four steps
- Create an app. Go to strava.com/settings/api with a Strava subscription. Note the Client ID and Client Secret. Set the Authorization Callback Domain to localhost while you build.
- Call the API with your own token. The settings page shows an access token for your own account, which changes every six hours.
curl -X GET \ https://www.strava.com/api/v3/athlete \ -H 'Authorization: Bearer YOURACCESSTOKEN' - Connect a real user. Send them to strava.com/oauth/authorize with only the scopes you need, such as activity:read. Swap the code for tokens at POST https://www.strava.com/oauth/token on your server, and save the scope Strava returns.
- Load history once, then listen. Page through GET /athlete/activities with the after filter, 30 items per page by default, while you watch the rate limit headers. Then create your one webhook subscription so new activities arrive without polling.
Terms you must know
Strava has two documents that work together. The API Agreement (effective June 1, 2026) sets the legal frame. The API Policy (also effective June 1, 2026) is "incorporated by reference into, and forms part of" the Agreement, and holds most of the operating rules. Both can change when Strava posts a new version, and continued use counts as consent (Agreement preamble and 14.4.1). We read both in full on November 10, 2026.
AI use (Policy 5.3)
You may not use Strava data "in connection with the development, training, evaluation, or operation of any AI Application". The ban covers derived, aggregated, anonymized and de-identified data. It lists training, fine-tuning, grounding, evaluation, embeddings, retrieval-augmented generation and "ingestion into a context window or working memory". The only exception is Strava's own MCP server, which Policy 3.5 calls "the sole authorized first-party agent-mediated interface". It is not a route for your product. We did not find a definition of "AI Application" in either document.
For a healthcare product, this rules out an AI care assistant, an AI triage step or an LLM summary that reads Strava workouts. For a wellness app, it rules out an AI coach on Strava data. Press reports from November 2024 said the earlier AI clause was about model training. The 2026 text goes well past training. Ask Strava in writing if your product has any AI feature that might touch this data, even indirectly.
Intermediaries and aggregators (Policy 5.16)
You may not "operate, offer, or facilitate any abstraction layer, integration-platform-as-a-service, no-code-AI platform, pass-through proxy, intermediary, or aggregator that re-exposes the Strava API Materials, in whole or in part, to third parties". You may not run an MCP server or agent interface over Strava data, re-use one API token across several services or end users, or build an app whose main purpose is to let others reach Strava data. Agreement 1.1 and 1.2 add that one token belongs to one app and may not be shared.
For both readers, this means you should connect to Strava under your own app registration and not count on an aggregator for Strava data. If an aggregator says it still offers Strava, ask to see Strava's written permission.
Storage and retention (Policies 5.5, 6.2, 6.3, 6.4, 7.4)
- Cache Strava data for no more than seven days (6.2). If a resource disappears from Strava, remove it from your cache at once.
- No "Persistent Index": no vector stores, search indexes, knowledge graphs or archives of Strava data (5.5). The seven-day cache is allowed only if you run it as a transient cache. No building up a corpus beyond what your app needs to run.
- When an athlete deletes something on Strava, remove it from your app within 48 hours (6.3).
- Keep data only as long as needed for its original purpose (6.4).
- On a user's request, revocation or account deletion, delete their Strava data and derived personal data within 30 days. On termination, delete everything (7.4 and Agreement 4.4), and certify in writing if asked.
Section 7.4 allows longer retention where "applicable law or an agreement with the affected user requires retention for a longer period", with proof kept for Strava. A healthcare team might read this as room for medical record retention rules. Section 6.2 still caps the cache at seven days. These two readings pull in different directions, so get Strava's answer in writing before you write Strava data into an EHR or clinical data store. For a wellness app, design screens that fetch on demand and expire after seven days.
No analytics or combining data (Policy 5.4)
You may not process Strava data, even de-identified, "for the purposes of analytics, analyses, customer insight generation, or product or service improvements". You "may not combine Strava Data with other customer data for these or any other purposes". For a healthcare product, that covers population reports, outcomes studies and merging workouts with clinical data. For a wellness app, it covers cohort dashboards and product analytics built on workout data.
Display and sharing (Agreement highlights, Policy 2.3, 5.10, 5.13, 6.1)
Strava data from a user may be shown "only to that user". You may not let anyone else see a user's data without that user's prior express consent (5.13). You may not sell, license or hand Strava data to third parties, including advertisers, data brokers, AI providers or model developers, "even if a user of your Developer Application consents" (5.10). Section 6.1 contains a sentence that begins "Unless your Developer Application has an athlete capacity of 9,999 or less", and then limits display to that user's own data. As written it seems to say the opposite of 2.3. Ask Strava what it means.
For a healthcare product, a clinician or coach view of a patient's Strava workouts needs Strava's confirmation. Section 5.13 suggests the patient's express consent may be enough for viewing. Section 5.10 and the highlights point the other way. For a wellness app, each athlete sees their own data. Leaderboards across users are out.
Medical use, PHI, HIPAA and BAA
Neither document has a clause on medical use, diagnosis, PHI, HIPAA or a BAA. Agreement 14.6 says each party is "a separate and independent controller" under GDPR. Policy 7.3 requires your privacy policy to meet GDPR and UK GDPR. Policy 5.14 requires you to follow laws on privacy, security and AI regulation. There is nothing that lets you send Strava data to Strava as PHI, and nothing that offers a BAA. For a covered entity, treat any Strava data you receive as your own PHI once it sits with patient identity, and run it under your own HIPAA program.
Branding and publicity (Agreement 8, Policy 4)
Follow the Brand Guidelines. Do not use Strava marks in your app's name, icon or logo (4.1). Do not imply endorsement (4.3). If you show data that came from a Garmin device, show Garmin's attribution (4.4). No press release that mentions Strava without written consent (4.6). Strava may use your app and marks to promote Strava (Agreement 9.5, Policy 4.5).
Competing products (Agreement highlights, Policy 5.2)
You may not compete with or replicate Strava, imitate its look, or use the API in a product that "features, endorses, or otherwise supports a third party that provides services competitive to Strava's products and services". A health platform that also connects other fitness apps might be read as supporting competitors. Ask Strava if your product lists rival activity apps beside Strava.
Charging users and ads (Policies 5.8, 5.9)
You may not charge users for Strava functionality or resell API access. You may charge for your own features that do not duplicate Strava. You may not use Strava data in ads or for targeted advertising.
Consent and user rights (Policies 2.1, 2.2, 2.5, 7.2)
Before you access data, your consent screen must state the data types, collection methods, how to withdraw consent, how to request deletion, and that you will confirm deletion. Users can ask to see what you collected (2.2). If you change what you collect, ask again (7.2).
Security, audit and notices
- Report a security breach to legal@strava.com within 24 hours of discovery (Policy 8.3).
- Report a leaked API token to developers@strava.com within 24 hours (Agreement 1.2).
- Tell Strava within 45 days if you are acquired or merge (Agreement 1.4).
- Strava may audit your app (Agreement 6.2) and ask for your subprocessor list with locations (Policy 7.7).
- Your privacy policy must say Strava may collect usage data about your API use (Policy 6.5).
Termination and liability (Agreement 2, 4, 13)
Strava may change or end API access at any time, for any reason, without notice (2.1, 4.2). On termination you must delete all Strava data, certify it, and tell your users (4.4). Strava's liability is capped at the greater of fees paid in the last year or $100 (13.2). You indemnify Strava (12.1). Law is California, venue San Francisco (14.1.1). For a healthcare program, write a plan for losing Strava overnight.
Cost and payment terms
- API fee: none today (Agreement 3.2). Strava may add charges, including "differentiated pricing for business users", with notice. If you do not accept new charges, you must stop using the API (3.3).
- Developer subscription: a Strava subscription is required to create an app (developer docs). Price not stated on the pages we read.
- End users: Standard Tier apps (up to 10 users, and up to 9,999 users) are subject to subscription requirements "as published on the Strava developer site" (Policy 3.3). The pages we read do not say which end users must subscribe. Extended Access Tier apps (10,000 or more) are not subject to subscription requirements unless Strava publishes otherwise.
- Enterprise contract or revenue share: not published.
- Aggregator cost: not relevant while Policy 5.16 applies.
Use cases
1. Athlete training log in a coaching app (wellness)
The athlete taps "Connect with Strava" and approves scopes. Strava sends an activity create event to your webhook. Your server fetches the activity and its streams, computes your own training load, and shows the result to that athlete only. Data used: activity summary, heart rate and power streams, zones.
- The athlete unticks activity:read_all, so "Only You" workouts are missing. Fix: read the returned scope and show a prompt explaining what is missing.
- Webhook slower than 2 seconds, so Strava retries and then drops the event. Fix: answer 200 at once and process from a queue.
- Stored workouts older than seven days. Fix: refetch on view and expire the cache.
2. Physio or sports medicine return-to-run plan (patient-facing)
The patient links Strava in the clinic's patient app. Each new run triggers a fetch. The app shows the patient their weekly distance and heart rate against the plan the clinician set. Data used: distance, moving time, heart rate streams.
- The clinician wants to see the runs. Fix: do not build that view until Strava confirms it in writing (Policy 2.3, 5.13).
- The clinic wants the runs in the EHR. Fix: get Strava's answer on Policy 6.2 and 7.4 first. Until then, record only what the patient reports to the clinician.
- No heart rate sensor. Fix: check
has_heartrateand fall back to pace.
3. Employer or payer activity challenge
Members connect Strava. Each activity event lets your app count minutes toward a personal goal, shown to that member. Data used: activity type, moving time.
- Leaderboards across members break Policy 2.3. Fix: personal progress only.
- Program reports to the employer break Policy 5.4. Fix: report only counts from your own non-Strava data, or ask Strava.
- Rate limits during a launch spike. Fix: rely on webhooks, throttle backfill using the X-RateLimit headers.
4. Clinical trial activity endpoint
A participant exports their Strava archive through the Bulk Data Export Tool and uploads it, or connects through OAuth for live sync. Data used: activities and streams.
- Live API data cannot form a stored research dataset (Policies 5.4, 5.5, 6.2). Fix: use the participant's own export, which Policy 6.6 protects, and check with your IRB and counsel.
- Export format not documented in what we read. Fix: test a real export before writing the protocol.
5. Cardiac rehab home exercise check-in
The patient links Strava in a rehab app. After each session the app shows the patient their heart rate against the target zone set in the app. Data used: heart rate stream, elapsed time.
- Any alert to the care team means showing data to a third party. Fix: confirm with Strava first, or let the patient forward their own summary.
- Strava is not a medical device and makes no accuracy promise (Agreement 11.2). Fix: do not use it for clinical decisions.
Strava data in an EHR or remote monitoring program
Healthcare teams often want workouts next to clinical data. The usual pattern is to turn each value into a FHIR Observation, the standard record for a measurement. With Strava, settle storage first. Policy 6.2 caps your cache at seven days, so ask Strava in writing before any value lands in a chart.
| Strava value | FHIR Observation | Code |
|---|---|---|
| heartrate stream, average_heartrate | Heart rate, beats per minute | LOINC 8867-4 |
| moving_time | Exercise duration, seconds | LOINC 55411-3 |
| calories | Calories burned, kilocalories | LOINC 41981-2 |
| distance | Distance, meters | LOINC 55412-1, exercise distance (checked 11 Nov 2026). It fits rides, runs and swims. |
| Athlete weight (profile) | Body weight, kilograms | LOINC 29463-7 |
| sport_type, power and segment efforts | Device-specific Observation | Your own code system. No standard code fits these exactly. |
Keep the Strava activity id on each Observation. A webhook delete event, or a deauthorization, must find and remove it, within 48 hours for display (Policy 6.3).
Known blockers and gotchas
- Seven-day cache. Most health data platforms store history. Strava allows a seven-day cache (Policy 6.2). Design for fetch on demand, and ask Strava about any longer retention.
- No AI. Policy 5.3 covers context windows and embeddings. Keep Strava data out of every AI pipeline, logs that feed AI tools included.
- Aggregators. Policy 5.16 bans re-exposing the API. Press reports in 2026 described the same change. Register your own app.
- One-user display. No clinician, coach or team views without Strava's written agreement.
- Subscription to build. The developer needs a Strava subscription to create an app. End-user subscription rules for Standard Tier are referenced but not spelled out on the pages we read.
- Review with no SLA. You cannot connect athlete 11 until Strava reviews you (Policy 3.6). Start the form early.
- Refresh token rotation. Each refresh may return a new refresh token and the old one stops working at once. Save the new one in the same transaction.
- Scopes can be unticked. Users can decline scopes on the consent screen. Check the granted scope on every token exchange.
- Webhook rules. One subscription per app. Answer 200 within 2 seconds. Up to 3 attempts. Handle deauthorization events by deleting data.
- Rate limits count failures. A request rejected by the 15-minute limit still counts against the daily limit. Daily limits reset at midnight UTC.
- Terms change by posting. Strava updates take effect when posted. Re-read the Agreement and Policy each quarter.
- Garmin attribution. Garmin-sourced data needs Garmin's attribution on screen (Policy 4.4).
Delivery timeline
Our estimate for a first integration, not a measured figure.
| Week | Work | Depends on Strava? |
|---|---|---|
| Before week 1 | Written questions to developers@strava.com on display, storage and AI for your use case | Yes. No published response time. |
| 1 | App registration, OAuth, token store with rotation, consent screen per Policy 2.1, webhook endpoint | No |
| 2 | Activity and stream fetch, seven-day cache with expiry, deletion within 48 hours, throttled backfill, brand-compliant screens | No |
| 2 to 3 | Screenshots and Developer Program submission | Yes. No SLA (Policy 3.6). |
| After approval | Rollout past 10 athletes, rate-limit monitoring | Yes |
Questions to ask Strava before you sign
- May a patient consent to a named clinician or coach seeing their Strava workouts in our app, under Policy 5.13?
- Does Policy 7.4's carve-out for retention required by law cover medical record rules, given the seven-day cache in Policy 6.2?
- What counts as an "AI Application" under Policy 5.3? Does a rules engine or a non-generative score count?
- Does a health platform that also connects other fitness apps "support a third party that provides services competitive to Strava" under Policy 5.2?
- What subscription must our end users hold at Standard Tier, and what does it cost?
- What does the first sentence of Policy 6.1 mean for an app under 9,999 athletes?
- Is there a typical review time for the Developer Program and for Extended Access?
- Will you confirm in writing that our use is permitted, given Policy 2.2 invites these questions?
Other device integration guides
Strava is often one source 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.
- Oura API integration guide
- WHOOP API integration guide
- Garmin API integration guide
- Ultrahuman API integration guide
- Eight Sleep API integration guide
- Fitbit and Google Health API integration guide
- Apple Health API integration guide
- Health Connect API integration guide
- Samsung Health API integration guide
- Withings API integration guide
- Dexcom API integration guide
- FreeStyle Libre API integration guide
- Polar API integration guide
- COROS API integration guide
- Suunto API integration guide
- Peloton API integration guide
- MyFitnessPal API integration guide
Ready to build your Strava integration?
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. Book a call about your device integration.
For whoever builds this
Auth
- OAuth 2.0 authorization code flow. Authorize at
https://www.strava.com/oauth/authorize, exchange and refresh atPOST https://www.strava.com/oauth/token. - Scopes:
read,read_all,profile:read_all,profile:write,activity:read,activity:read_all,activity:write. Users can untick any of them. Store the scope actually granted. - Access tokens last 6 hours. Refresh with
grant_type=refresh_token. If more than 1 hour remains, the same access token comes back. A new refresh token may come back and the old one is invalid at once. - One API token per app. Never share it across services or tenants (Agreement 1.1, 1.2, Policy 5.16(c)).
Endpoints (base https://www.strava.com/api/v3)
GET /athlete,PUT /athlete(weight with profile:write), athlete zones and stats.GET /athlete/activities(paged, before and after filters),GET /activities/{id}, laps, zones.GET /activities/{id}/streams?keys=...&key_by_type=true. Stream keys: time, distance, latlng, altitude, velocity_smooth, heartrate, cadence, watts, temp, moving, grade_smooth. Needs activity:read, or activity:read_all for Only Me activities.POST /activities,POST /uploadsfor writes.
Rate limits
- Default: overall 200 per 15 minutes and 2,000 per day. Non-upload ("read") 100 per 15 minutes and 1,000 per day.
- After self-upgrade to 10 athletes: overall 400 per 15 minutes and 4,000 per day. Read 200 per 15 minutes and 2,000 per day.
- Windows reset at :00, :15, :30, :45. Daily reset at midnight UTC. 429 on breach. Read
X-RateLimit-Limit,X-RateLimit-Usage,X-ReadRateLimit-Limit,X-ReadRateLimit-Usage.
Webhooks
- One subscription per app. Events: activity create, update, delete, and athlete deauthorization.
- Respond 200 within 2 seconds. Up to 3 delivery attempts.
- Payload signing: the webhooks page describes no signature on event POSTs. The only shared secret is the verify_token, used once when the subscription is created. Validate by looking up the object ID through the API with the athlete's token.
- On delete or deauthorize: purge within 48 hours for display (Policy 6.3) and within 30 days from all systems (Policy 7.4).
Storage design
- TTL of 7 days on every Strava record. No search index, vector store or warehouse copy. Keep Strava data out of logs shipped to analytics or AI tools.
FHIR mapping (only if Strava confirms storage is allowed)
| Strava field | LOINC | Status |
|---|---|---|
| distance | 55412-1 exercise distance | Checked in LOINC 11 Nov 2026. Earlier we listed 55430-3, which is a pedometer walking code. |
| calories | 41981-2 | Unverified |
| moving_time | 55411-3 exercise duration | Unverified |
| heartrate stream, average_heartrate | 8867-4 | Unverified |
| athlete weight | 29463-7 | Unverified |
Version notes
- API v3. API Agreement and API Policy both effective June 1, 2026. The developer docs say the Agreement was "last updated June 1, 2026".
- November 2024 changes (effective November 11, 2024) were reported in the press as display and AI-training limits. The 2026 Policy replaces and widens them.
Sources
- Strava and Apple Health, https://support.strava.com/en-us/articles/15402024-apple-health-and-strava, read 10 November 2026.
- Strava and Health Connect, https://support.strava.com/en-us/articles/15401554-health-connect-and-strava, read 10 November 2026.
- Strava API Policy, effective 1 June 2026, sections 5.3 and 5.16, https://www.strava.com/legal/api_policy, 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.
- Strava API Agreement (2026), https://www.strava.com/legal/api, read in full November 10, 2026
- Strava API Policy, https://www.strava.com/legal/api_policy, read in full November 10, 2026
- Strava rate limits, https://developers.strava.com/docs/rate-limits/, read November 10, 2026
- Strava getting started, https://developers.strava.com/docs/getting-started/, read November 10, 2026
- Strava API reference, https://developers.strava.com/docs/reference/, read November 10, 2026
- Strava authentication, https://developers.strava.com/docs/authentication/, read November 10, 2026
- Strava webhooks, https://developers.strava.com/docs/webhooks/, read November 10, 2026
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Strava have a public API?
Is the Strava API free?
How many users can a new Strava app connect?
Can I use Strava data with AI?
Can I get Strava data through an aggregator like Terra or ROOK?
How long can I store Strava data?
Can a clinician or coach see a patient's Strava workouts?
Will Strava sign a BAA or does it address HIPAA?
What data does the Strava API expose?
What are the Strava API rate limits?
How long does a Strava integration take to build?
Which OAuth scopes does the Strava API use?
How much history do I get when a user first connects?
Which Strava changes trigger a webhook?
Why did my app get a delete event for an activity that still exists?
What units does the Strava API return?
How do I disconnect a user from my Strava app?


