Strava API v3

Name: Strava API v3 API
Brand: Strava API v3
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliveryoauth234 EndpointsREST

For Agents

Programmatically create an activity, get activity. Covers 34 operations 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.

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

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 instance

Jentic 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

GET STARTED

Start building with Strava API v3 API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

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

Strava API v3

Connect the Strava API v3 to your agent

Capabilities

Start building with Strava API v3 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs