Strava
Connect Strava to the rest of your business, with the right person approving what changes and a record of every action.
20 ways to read, 1 way to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Strava, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Update activity name or description
activities.updateApproval by rule - List athlete activities
activities.listRead
Example flow
- Strava · List athlete activities
activities.listDone - Strava · Update activity name or description
activities.updateMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Strava.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Strava
- Strava's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Strava athlete, stats, activities with laps, zones, comments, kudos and streams, segments, efforts, routes, clubs and gear, plus activity name and description edits.
Strava API docs- Source actions
- 20
- Destination actions
- 1
- Data types
- 14
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
activities3
- Get activitySource
Read one activity with description, calories and gear.
- List athlete activitiesSourceIncremental
Read the authorised athlete's activities, newest first, optionally in a time window.
- Update activity name or descriptionDestinationProvider duplicate protectionApproval before production
Change an activity's name and/or description. No other field is sent.
activity comments1
- List activity commentsSource
Read comments on one activity (first page).
activity kudos1
- List activity kudosSource
Read athletes who gave kudos to one activity.
activity laps1
- List activity lapsSource
Read the laps of one activity.
activity streams1
- Get activity streamsSource
Read time-series streams (time, distance, heart rate, power ...) for one activity.
activity zones1
- List activity zonesSource
Read time in heart-rate and power zones for one activity (Strava subscription feature).
athlete stats1
- Get athlete statsSource
Read recent, year-to-date and all-time totals for the authorised athlete.
athlete zones1
- Get athlete zonesSource
Read heart-rate and power zones (profile:read_all).
athlete1
- Get authorised athleteSource
Read the athlete authorised by this token; profile:read_all adds detail.
clubs2
- Get clubSource
Read one club.
- List athlete clubsSource
Read clubs the authorised athlete belongs to.
gear1
- Get gearSource
Read a bike or pair of shoes owned by the authorised athlete.
routes2
- Get routeSource
Read one route.
- List athlete routesSource
Read routes created by the authorised athlete.
segment efforts2
- Get segment effortSource
Read one segment effort.
- List segment effortsSource
Read the authorised athlete's efforts on one segment (Strava subscription feature).
segments3
- Get segmentSource
Read one segment.
- List starred segmentsSource
Read segments the authorised athlete has starred.
- Explore segmentsSource
Find the top segments inside a bounding box.
Access and limits
- Authentication
- Strava OAuth access token
- Plans and access
- Strava API application with the athlete's OAuth consent. Use is governed by the Strava API Agreement. Scopes needed: read and profile:read_all for the athlete, activity:read or activity:read_all for activities, activity:write only for activity edits.
- Test environment
- Use a test athlete account.
- Rate limits
- Strava applies per-application 15-minute and daily request limits (separate, lower limits for non-upload reads). HTTP 429 uses bounded retries and Retry-After.
- Pagination
- List endpoints use page and per_page (maximum 200).
- Provider events
- Strava webhook subscriptions push activity and athlete events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Access tokens expire after six hours and are not refreshed automatically; replace the stored token or reconnect the athlete.
- Excluded: uploads, manual activity creation, segment starring, athlete weight updates, route GPX/TCX exports and all deletes.
- Activity updates change only the name and description.
- Coordinates and map polylines are not returned to limit location exposure.
- Activity comments return one page (Strava's cursor for comments is not documented in the public schema).
- Strava's API Agreement restricts how athlete data may be displayed and shared; customers remain responsible for compliance.
Developer reference
- Create the Strava credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Strava, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/strava and the Connections API.