# Contact Center APIs do not provide modified\_date / insert\_date for incremental synchronization

**URL:** <https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410>\
**Category:** Contact Center\
**Created:** [June 24, 2026, 8:26am UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410 "2026-06-24T08:26:13Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paulo1](https://avatars.discourse-cdn.com/v4/letter/p/da6949/32.png) [@Paulo1](https://devforum.zoom.us/u/Paulo1)\
**Post date:** [June 24, 2026, 8:26am UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/1 "2026-06-24T08:26:13Z")

</div>

**Issue: Contact Center APIs do not provide modified\_date / insert\_date for incremental synchronization**

Hello Zoom Developer Community,

I am facing a data consistency issue when consuming Zoom Contact Center APIs and would like to understand the recommended approach for handling late-arriving or updated records.

Currently, the endpoints I use do not expose fields such as `modified_date`, `updated_at`, `created_at`, or `insert_date`. Because of this limitation, my incremental load strategy is based on the `start_time` field.

My current process is:

1. Retrieve the latest `start_time` stored in my database.

2. Subtract 2 hours from that timestamp as a safety window.

3. Use the adjusted timestamp as the API `from` parameter.

4. Use the current timestamp as the API `to` parameter.

5. All requests are made without specifying a timezone, so everything is handled in UTC.

However, I have noticed that when I reprocess historical periods, records that were previously loaded are returned with updated values, causing my database records to be updated. This suggests that the data available through the Zoom API can change after the original event occurred.

The challenge is that, without a field indicating when a record was created or last modified, it is impossible to reliably identify which records have changed since the last synchronization. Using `start_time` alone does not capture updates made to older records.

My questions are:

- Is there any recommended strategy for incremental synchronization of Contact Center data?

- Are there plans to expose fields such as `modified_date`, `updated_at`, or similar metadata in Contact Center reporting endpoints?

- Is there another endpoint or mechanism that allows consumers to identify records that were updated after their original `start_time`?

Any guidance would be greatly appreciated, as this limitation makes it difficult to guarantee data consistency in downstream analytics and data warehouse environments.

Thank you.

---

<div class="post-metadata">

**Author:** ![Paulo1](https://avatars.discourse-cdn.com/v4/letter/p/da6949/32.png) [@Paulo1](https://devforum.zoom.us/u/Paulo1)\
**Post date:** [July 10, 2026, 6:02pm UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/2 "2026-07-10T18:02:10Z")

</div>

Is there any suggestion?

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [July 13, 2026, 11:10pm UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/3 "2026-07-13T23:10:25Z")

</div>

Hi @rehema.zoom is this something you could test please and get back to @Paulo1 ? Thank you!

---

<div class="post-metadata">

**Author:** ![Paulo1](https://avatars.discourse-cdn.com/v4/letter/p/da6949/32.png) [@Paulo1](https://devforum.zoom.us/u/Paulo1)\
**Post date:** [August 26, 2026, 7:44pm UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/5 "2026-08-26T19:44:40Z")

</div>

Hi there. @gianni.zoom @rehema.zoom Is there any updates?

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [August 31, 2026, 6:06pm UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/6 "2026-08-31T18:06:23Z")

</div>

@Paulo1 Rehema is gonna get back to you soon! Thanks for following up!

---

<div class="post-metadata">

**Author:** ![rehema.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rehema.zoom/32/40323_2.png) [@rehema.zoom](https://devforum.zoom.us/u/rehema.zoom)\
**Post date:** [September 1, 2026, 12:50am UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/7 "2026-09-01T00:50:15Z")

</div>

Hi @Paulo1 ,

Are there specific endpoints that you are working with? Or is this concern regarding all reporting endpoints? If specific ones, please list them in your reply. In regard to exposing the named fields, I will speak to the team about this as a feature request.

Best,  
Rehema

---

<div class="post-metadata">

**Author:** ![Paulo1](https://avatars.discourse-cdn.com/v4/letter/p/da6949/32.png) [@Paulo1](https://devforum.zoom.us/u/Paulo1)\
**Post date:** [September 2, 2026, 5:41pm UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/8 "2026-09-02T17:41:40Z")

</div>

This concern applies to pretty much all of the Contact Center reporting endpoints I am currently using. All of the endpoints below have the same limitation: they do not provide a reliable `modified_date`, `updated_at`, `created_at`, `insert_date`, or similar field that can be used as a reference for incremental synchronization and detecting changes to previously returned records.

The specific endpoints I am working with are:

- `/contact_center/engagements`
- `/contact_center/voice_calls`
- `/contact_center/analytics/dataset/historical/agent_performance`
- `/contact_center/analytics/dataset/historical/agent_timecard`
- `/contact_center/analytics/dataset/historical/queue_performance`
- `/contact_center/analytics/dataset/historical/flow_performance`
- `/contact_center/analytics/dataset/historical/engagement`
- `/contact_center/analytics/dataset/historical/outbound_dialer_performance`
- `/contact_center/variable_logs`
- `/qm/evaluation`
- `/qm/automated_evaluations`
- `/qm/interactions`

In all of these cases, I currently have to rely on the event’s `start_time` as the reference point for incremental synchronization. However, as mentioned in my original post, records associated with older `start_time` values can subsequently be returned with different values when the same historical period is queried again.

So the main issue is not simply identifying new records, but also reliably detecting **changes to records that were already retrieved**.

I appreciate you raising this with the team as a feature request. Having a field such as `modified_date` or `updated_at` would make incremental synchronization much more reliable and would allow downstream systems and data warehouses to maintain data consistency.

---

<div class="post-metadata">

**Author:** ![rehema.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rehema.zoom/32/40323_2.png) [@rehema.zoom](https://devforum.zoom.us/u/rehema.zoom)\
**Post date:** [September 8, 2026, 1:11pm UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/9 "2026-09-08T13:11:39Z")

</div>

thank you for thorough response @Paulo1. These will be added details for the FR.

---

<div class="post-metadata">

**Author:** ![Paulo1](https://avatars.discourse-cdn.com/v4/letter/p/da6949/32.png) [@Paulo1](https://devforum.zoom.us/u/Paulo1)\
**Post date:** [October 22, 2026, 7:05pm UTC](https://devforum.zoom.us/t/contact-center-apis-do-not-provide-modified-date-insert-date-for-incremental-synchronization/144410/10 "2026-10-22T19:05:56Z")

</div>

@rehema.zoom hi!! Any updates?
