Strava API v3
★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliveryoauth234 EndpointsREST
For Agents
Programmatically create an activity, get activity. Covers 34 operations with oauth2 authentication.
Use for: I need to an activity, I want to activity, Search for activity, Find all activity comments
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
The [Swagger Playground](https://developers.strava.com/playground) is the easiest way to familiarize yourself with the Strava API by submitting HTTP requests and observing the responses before you write any client code. It will show what a response will look like with different endpoints depending on the authorization scope you receive from your athletes. To use the Playground, go to https://www.s. The API exposes 34 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the Strava API v3 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Strava API v3, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Strava API v3 API.
Create an Activity
Get Activity
Update Activity
List Activity Comments
Monitor Strava API v3 operational status and events
Use Cases
Patterns agents use Strava API v3 API for, with concrete tasks.
★ Communications Operations
Use the Strava API v3 to perform communications operations programmatically. The API provides 34 endpoints covering core functionality including create an activity, get activity, update activity.
Call POST /activities to create an activity
Automated Activities Management
Automate activities operations by combining multiple Strava API v3 endpoints. Agents can get activity and then update activity in a single workflow.
Call GET /activities/{id} to get activity, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Strava API v3 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.
Search Jentic for 'create an activity', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
34 endpoints — the [swagger playground](https://developers.
METHOD
PATH
DESCRIPTION
POST
/activities
Create an Activity
GET
/activities/{id}
Get Activity
PUT
/activities/{id}
Update Activity
GET
/activities/{id}/comments
List Activity Comments
GET
/activities/{id}/kudos
List Activity Kudoers
GET
/activities/{id}/laps
List Activity Laps
GET
/activities/{id}/streams
Get Activity Streams
GET
/activities/{id}/zones
Get Activity Zones
POST
/activities
Create an Activity
GET
/activities/{id}
Get Activity
PUT
/activities/{id}
Update Activity
GET
/activities/{id}/comments
List Activity Comments
GET
/activities/{id}/kudos
List Activity Kudoers
GET
/activities/{id}/laps
List Activity Laps
GET
/activities/{id}/streams
Get Activity Streams
GET
/activities/{id}/zones
Get Activity Zones
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Strava API v3 oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create an activity') and Jentic returns the matching Strava API v3 operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Strava API v3 integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Strava API v3 API through Jentic.
What authentication does the Strava API v3 use?
The Strava API v3 uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I create an activity with the Strava API v3?
Yes. Use the POST /activities endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Strava API v3?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create an activity through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create an activity'. Jentic returns the matching Strava API v3 operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Strava API v3 have?
The Strava API v3 exposes 34 endpoints covering activities, athlete, athletes operations.
GET STARTED