AsyncAPI channel · Strava · Strava Webhooks API

webhook/callback

Single callback endpoint registered for the application's push subscription. Receives both the one-time GET validation challenge and ongoing POST event deliveries. Each application maintains one subscription that receives events for all authorized athletes.

Open source AsyncAPI → All Strava channels Strava provider profile
Provider: Strava AsyncAPI: v2.6.0 Spec: Strava Webhooks API Operations: 2 Messages: 2

Channel address

webhook/callback

Operations

publish
respondToValidationChallenge
Respond to the Strava subscription validation challenge
receiveWebhookEvent
Receive a Strava webhook event delivery

Messages

ValidationChallengeResponse
JSON body returned by the subscriber in response to Strava's GET validation request, echoing the supplied hub.challenge.
Content-Type: application/json
WebhookEvent
Event envelope POSTed by Strava to the subscriber callback URL.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.