Please add start_date / start_date_local to Club Activities API response

Hi Strava Developer Team,

I’m building a small internal company challenge app based on Strava Clubs. We have separate clubs for running, cycling, and swimming, and the goal is to aggregate club activities for a fixed challenge period and display leaderboards per discipline.

I’m using the Club Activities endpoint:

GET /api/v3/clubs/{clubId}/activities

The endpoint returns useful summary fields such as:

{
  "resource_state": 2,
  "athlete": {
    "resource_state": 2,
    "firstname": "Marcin",
    "lastname": "G."
  },
  "name": "Evening Swim",
  "distance": 1300.0,
  "moving_time": 1575,
  "elapsed_time": 2193,
  "total_elevation_gain": 0,
  "type": "Swim",
  "sport_type": "Swim",
  "device_name": "Garmin Forerunner 570"
}

However, the response does not seem to include any activity date field, such as:

"start_date"
"start_date_local"

This makes it difficult or impossible to reliably filter club activities by a custom challenge date range, for example:

2026-07-01 to 2026-08-31

The Strava web UI clearly shows when the activity happened, but the Club Activities API response does not expose that date. Without this field, developers have to either import activities with the current sync timestamp or use fragile workarounds, which makes leaderboard calculations inaccurate.

Would it be possible to add one of the following fields to the Club Activities API response?

"start_date": "2026-07-02T16:27:00Z",
"start_date_local": "2026-07-02T18:27:00Z"

Even just start_date would be enough.

This would make the Club Activities endpoint much more useful for club-based challenges, internal wellness competitions, and community leaderboards, while still keeping the response lightweight.

Thanks!