Hi Oura team,

I'm a developer building a personal cycle-syncing planner on top of the Oura API v2. The API currently exposes the raw temperature signal (temperature_deviation, temperature_trend_deviation) but not the computed Cycle Insights layer, which is in-app only. I'd love to see that surfaced as a read endpoint.

Specifically, a daily_cycle_phases (or cycle_insights) endpoint returning, per day:

cycle_phase — menstrual / follicular / ovulatory / luteal

cycle_day — day within the current cycle

period_window_prediction — the 5-day predicted onset window

fertile_window_start / fertile_window_end

ovulation_day — detected or predicted

cycle_length / period_length — rolling averages

source — detected / predicted / user-logged

Use case: cycle phase-aware daily planning (energy, scheduling, reflection). Right now I either ask users to log periods manually or re-derive phases from temperature trends, which duplicates work Oura already does far better. Read-only access with the user's consent would be ideal, and matching the existing daily-summary response shape would make integration trivial.

Happy to be a test integration if useful. Thanks for considering it!