Currently, the GET /v1/events endpoint includes a "period" parameter that supports the following enum values:

While these values are useful, they are quite limited. Expanding this parameter to support custom date ranges would significantly enhance its flexibility and utility.

A good reference for such a feature is Plausible’s implementation of date ranges in their API: https://plausible.io/docs/stats-api#time-periods. Their approach provides minimal but effective date range functionality that could greatly improve the relevance of the results.

The need for this enhancement stems from my current task of aggregating analytics statistics from different services for our organization. In SavvyCal's case, I need to request all events and manually filter them for specific date ranges. This approach results in considerable overhead and inefficiency.

Adding support for custom date ranges directly in the API would streamline this process and reduce unnecessary data processing.