Strava challenges API

Endpoint facts

Method

GET

API path

/strava/challenges

Auth

apiKey

Credits

1 credit/request

Platform

Strava

Response schema

#/definitions/strava.challengesResponseDoc

Overview

Returns Strava's public challenge gallery: the currently promoted challenge plus every gallery section (partner challenges, and one section per sport such as run/ride), each with its challenges' goal, duration, and cover art. Public data, sourced from Strava's own challenge gallery. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- `sections` is ordered with `partner` first, then the remaining sport categories alphabetically. - A challenge's `goal` is `null` for challenges measured by elapsed time rather than a fixed distance/duration target (e.g. "fastest mile ever"). Example response: ```json { "code": 200, "msg": "OK", "data": { "promoted_challenge": { "id": 6158, "name": "August Flexibility Challenge", "url": "https://www.strava.com/challenges/August-Flexibility-Challenge", "sponsored": false, "goal": 36000, "dimension": "moving_time", "icon": "yoga", "duration": "Aug 1, 2026 to Aug 31, 2026", "goal_description": "Complete 10 hours of yoga or workout activity this month." }, "sections": [ { "category": "partner", "title": "Partner Challenges", "challenges": [ { "id": 6156, "name": "Runna August Ten Days Active Challenge", "url": "https://www.strava.com/challenges/Runna-August-Ten-Days-Active-2026", "sponsored": true, "goal": 10, "dimension": "moving_time", "duration": "Aug 1, 2026 to Aug 31, 2026" } ] }, { "category": "run", "title": "Run Challenges", "challenges": [ { "id": 6162, "name": "August 10K Challenge", "url": "https://www.strava.com/challenges/August-10K-challenge-2026", "sponsored": false, "goal": 10000, "dimension": "avg_pace_min_distance", "duration": "Aug 1, 2026 to Aug 31, 2026", "goal_description": "Complete a 10 km (6.2 mi) run." } ] } ], "source_url": "https://www.strava.com/challenges" } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related