# Intervals.icu API Integration Cookbook

**URL:** <https://forum.intervals.icu/t/intervals-icu-api-integration-cookbook/80090>\
**Category:** Guide\
**Created:** [20 November 2024 10:25 UTC](https://forum.intervals.icu/t/intervals-icu-api-integration-cookbook/80090 "2024-11-20T10:25:24Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![stezz](https://forum.intervals.icu/user_avatar/forum.intervals.icu/stezz/32/47977_2.png) [@stezz](https://forum.intervals.icu/u/stezz)\
**Post date:** [14 February 2025 16:01 UTC](https://forum.intervals.icu/t/intervals-icu-api-integration-cookbook/80090/5 "2025-02-14T16:01:30Z")

</div>

@david I am trying to fix old data for `avg_sleep_hr` in the wellness data pre 07/02/25 (see [why here](https://forum.intervals.icu/t/oura-avg-sleep-hr-vs-lowest-resting-hr/85963/15)). I have tried to use both `wellness-bulk` and `wellness` endpoints but what is happening is that I can see the data being modified in the UI for a moment, and a moment later it goes back to what it was before, like the system was reverting any change made via the API to what it gets from Oura anyway.

Is this expected? I read [here](https://forum.intervals.icu/t/oura-ring-integration/4288/30) that

> Intervals.icu goes back about a week for Oura

But it seems, it only works if you modify that via the UI?

Can you please help me to understand?

Ps. if you wanted to fix you sync algorithm so that it does that by itself I am all happy 😃

---

_[View the full topic](https://forum.intervals.icu/t/intervals-icu-api-integration-cookbook/80090)._