# Provide both manual and calculated event load in API

**URL:** <https://forum.intervals.icu/t/provide-both-manual-and-calculated-event-load-in-api/133249>\
**Category:** Feature Requests\
**Created:** [25 October 2026 15:46 UTC](https://forum.intervals.icu/t/provide-both-manual-and-calculated-event-load-in-api/133249 "2026-10-25T15:46:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Another\_Intervaler](https://forum.intervals.icu/letter_avatar_proxy/v4/letter/a/f05b48/32.png) [@Another\_Intervaler](https://forum.intervals.icu/u/Another_Intervaler)\
**Post date:** [25 October 2026 15:46 UTC](https://forum.intervals.icu/t/provide-both-manual-and-calculated-event-load-in-api/133249/1 "2026-10-25T15:46:13Z")

</div>

We thankfully can override the calculated load of a planned event via the API by PUT’ing a new value for icu\_training\_load (or of course manually in the GUI). On future GET requests, the overriden load is returned, just as it should be.

It would be great if the API, on subsequent calls, returned both the manual icu\_training\_load (as now) and the originally calculated value (or probably better yet the value that would be calculated right now, which could be different if zones or other settings were changed).

This value is what would be practical for people that do their own load calulations to have in the API - maybe a new attribute icu\_training\_load\_calc or something like along those lines.

---

<div class="post-metadata">

**Author:** ![R2Tom](https://forum.intervals.icu/user_avatar/forum.intervals.icu/r2tom/32/50144_2.png) [@R2Tom](https://forum.intervals.icu/u/R2Tom)\
**Post date:** [25 October 2026 16:28 UTC](https://forum.intervals.icu/t/provide-both-manual-and-calculated-event-load-in-api/133249/2 "2026-10-25T16:28:55Z")

</div>

You get the original fields from these values

 ![image](https://forum.intervals.icu/uploads/default/original/3X/0/8/0831aad773d8b510bc1337a05bd21f3f508370d7.png)