# API response data is not consistent with the UI

**URL:** <https://community.dynatrace.com/t/api-response-data-is-not-consistent-with-the-ui/39063>\
**Category:** Dynatrace API\
**Tags:** dynatrace-managed, dynatrace-api\
**Created:** [March 29, 2023, 5:23am UTC](https://community.dynatrace.com/t/api-response-data-is-not-consistent-with-the-ui/39063 "2023-03-29T05:23:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Quirina](https://avatars.discourse-cdn.com/v4/letter/q/8797f3/32.png) [@Quirina](https://community.dynatrace.com/u/Quirina)\
**Post date:** [March 29, 2023, 5:23am UTC](https://community.dynatrace.com/t/api-response-data-is-not-consistent-with-the-ui/39063/1 "2023-03-29T05:23:34Z")

</div>

Hi everyone,

I encountered one problem:&nbsp;It’s regarding the monitor response timestamp is not consistent with the monitor actual execution time.

Monitor url: https://{environmentid}.live.dynatrace.com/#monitoranalysiskpm;webcheckId=SYNTHETIC\_TEST-5A94A13245AB6F4E;actionType=Load;event=SYNTHETIC\_TEST\_STEP-44E613EA9274FA08;splitting=metric;analysisTf=custom1679977606244to1679984806244;mode=performance;analysisActionType=Load;filterEvent=SYNTHETIC\_TEST\_STEP-44E613EA9274FA08;gtf=-6h

My requirement is that I want to search the duration and its specific execution time of this monitor from 2023-3-20 00:00:00 to 2023-3-20 23:59:59

But the actual timestamp is not consistent with the API response timestamp

 ![Quirina_0-1680067390833.png](https://global.discourse-cdn.com/dynatrace/original/3X/1/9/1939a4ab7871ea4b9ad8ecb23022421d90492e94.png)

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [May 25, 2023, 7:23pm UTC](https://community.dynatrace.com/t/api-response-data-is-not-consistent-with-the-ui/39063/2 "2023-05-25T19:23:24Z")

</div>

Synthetics can be a bit tricky but its important to note several things:

- API time is in UTC and not in Your timezone

- UI Data is in your timezone

- Synthetics run in a staggered fashion - 1 at a time dependent on frequency and locations. Example: I have synthetics run every 1 min from 2 locations. When 8am hits, Synthetics will not trigger both locations at the same time, Rather the frequency (1 Min) is divided by the number of locations (2) = Time each location runs… so 1 / 2 = 0.5 Which is every 30 seconds a location runs. Now Dynatrace will not show you seconds in the UI, rather its rounded up/down, but it will be depicted accurate in the API
