Stride

Search Documentation

Search for articles, guides, and more

← API overview

Get an activity's laps and segments

GET/v1/activities/{activity_id}/lapsrequires activities.read

The structure the recording was divided into: laps as the head unit marked them, plus the climbs, descents and corners Stride detected, each with its own duration, distance and averages.

This is the segments block of the full analysis, on its own. Fetch it rather than the whole activity when all you want is the shape of the session.

Path parameters

  • activity_idstringrequired

    The activity ID, e.g. `act_2f...`. The owner is resolved from it.

Example

bash
curl -X GET "https://api.stride.is/v1/activities/{activity_id}/laps" \
  -H "Authorization: Bearer $STRIDE_TOKEN"

Response 200

Success.

A free-form object whose shape depends on the request.

Errors

Every error is an RFC 9457 problem document. Branch on its code, which is stable; detail is prose and may be reworded.

  • 400The request was malformed: an unparseable date, an unknown enum value, or a parameter combination that cannot be satisfied.
  • 401No access token was supplied, or it is not valid for this API.
  • 402The Stride account the token belongs to has no active subscription or trial.
  • 403The token does not hold the scope this endpoint requires, or may not act on the athlete or team named.
  • 404No such resource, or it is not visible to this token. The two are deliberately indistinguishable.
  • 405The path exists but does not serve this method. The Allow header lists the ones it does.
  • 429A rate limit was exceeded. Retry after the period in the Retry-After header.
  • 500Something failed on Stride's side. The failure is logged with a trace ID.