# Difference in ical\_uid received in Nylas webhook

**URL:** <https://forums.nylas.com/t/difference-in-ical-uid-received-in-nylas-webhook/929>\
**Category:** Question and Answers\
**Tags:** webhooks, calendar-api, events\
**Created:** [September 22, 2025, 5:35pm UTC](https://forums.nylas.com/t/difference-in-ical-uid-received-in-nylas-webhook/929 "2025-09-22T17:35:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lsr2001](https://avatars.discourse-cdn.com/v4/letter/l/f6c823/32.png) [@lsr2001](https://forums.nylas.com/u/lsr2001)\
**Post date:** [September 22, 2025, 5:35pm UTC](https://forums.nylas.com/t/difference-in-ical-uid-received-in-nylas-webhook/929/1 "2025-09-22T17:35:24Z")

</div>

I have subscribed to calendar events related webhook. Now the ical\_uid which I receive in webhook payload for Microsoft events are different to what I receive in Nylas events list API. This is happening in case of recurring events when I try to edit individual instances. How to handle this scenario as I want to edit events which I have stored using Nylas events API and now there’s no way to track.

---

<div class="post-metadata">

**Author:** ![jean1199](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@jean1199](https://forums.nylas.com/u/jean1199)\
**Post date:** [October 2, 2025, 3:35am UTC](https://forums.nylas.com/t/difference-in-ical-uid-received-in-nylas-webhook/929/2 "2025-10-02T03:35:59Z")

</div>

Hi Isr2001,

What you’re experiencing is actually expected behavior for recurring events with Microsoft and Google providers.Each instances in a recurrence series have their own unique `ical_uid` that’s different from the master event’s `ical_uid`.

When you edit a single occurrence of a recurring event, Nylas creates what we call an “override” event. These override events represent the modified instances in a recurrence series and they get their own unique `ical_uid` also different from the master event’s `ical_uid`.

This is why you’re seeing different values between your webhook payload and the Events API response.

Keep in mind that the `ical_uid` represents an event/meeting across different calendars, so it makes sense that different instances with different schedules have each an uniques `ical_uid`.