canonical: https://jentic.com/apis/strava.com/strava

# Strava API v3

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.

## For AI agents

Programmatically create an activity, get activity. Covers 34 operations with oauth2 authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Create an Activity
- Get Activity
- Update Activity
- List Activity Comments
- Monitor Strava API v3 operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create an activity', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Activities** — Operations for activities
- **Athlete** — Operations for athlete
- **Athletes** — Operations for athletes
- **Clubs** — Operations for clubs
- **Gear** — Operations for gear

## Why Jentic

- **Setup:** Wiring the Strava API v3 by hand means running its OAuth2 flow, refreshing scoped tokens for calls to www.strava.com/api/v3, and paging activity and club streams yourself. Through Jentic you install once, import the Strava API v3 from the API Directory, store the OAuth credentials once, and your agent calls it.
- **Permission scoping:** Strava puts the activity id in the URL path (/activities/{id}/...), so a rule can pin your agent to reading one activity's comments, kudos, and laps. You choose the operations it may call, so creating or updating activities is not included unless you add it.
- **Credential handling:** Your Strava OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an activity's kudos' or 'list the authenticated athlete's activities', and Jentic returns the matching Strava API v3 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Strava API v3?

Yes. Because Jentic One is self-hosted, your own rules decide which Strava operations and OAuth credentials the agent may use. Since Strava puts the activity id in the URL path (/activities/{id}/...), you can pin the agent to read-only calls such as listing one activity's comments, kudos, and laps. Write operations like POST /activities or PUT /activities/{id} stay off limits unless you explicitly add them.