Get the authenticated athlete
/v1/athleterequires athlete.readThe athlete this token belongs to: their name, timezone, unit preference, connected device integrations and subscription status.
timezone is worth reading first. Stride records an activity's start as local wall-clock time, so a session that began at nine in the morning is timestamped 09:00:00Z wherever the athlete was. Use this field to interpret every timestamp the API returns.
email is only present when the token holds the athlete.email scope.
Example
curl -X GET "https://api.stride.is/v1/athlete" \
-H "Authorization: Bearer $STRIDE_TOKEN"Response 200
Success.
connected_integrationsstring[]always presentDevice and service integrations the athlete has connected, e.g. garmin, wahoo, whoop.
emailstringhas_subscriptionbooleanalways presentidstringalways presentnamestringtimezonestringIANA timezone name, e.g. Europe/London. Every activity timestamp is local wall-clock time and must be read against this.
uses_metric_unitsbooleanalways presentHow the athlete prefers Stride's own apps to display values. It does not change what this API returns, which is always SI.
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.