Difference in ical_uid received in Nylas webhook

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.

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.