Skip to main content

When we reschedule an event in calendly and then call scheduled_events end point in API, it returns two events, one with status cancelled with older time slot and another with status active with new time slots.

 

In this case how can i infer that the second event in actually the reschedule of first event?

Hey @Madan71582,

When an event is rescheduled in our system, we cancel the event and then create a new event.

Returning both events is the expected behavior for the /scheduled_events endpoint. We don’t currently return any sort of data that would allow you to associate the the canceled event with the newly created event.

One workaround might be to filter by the event status. For instance, you can pass ‘status=active’ and the endpoint will only return active events. This should eliminate the additional data that you’re seeing.

https://developer.calendly.com/api-docs/2d5ed9bbd2952-list-events

 

 


Hi @anolson Here is my use case:

My end users schedule an event in my application through calendly embed. I store the event id and time information. After that the user goes to calendly site and reschedules that. This needs to be synced from my side for which i cannot use webhook since my user will have his own account and organization which will not be in paid tier.

Only way is i have to send api calls to check if the event in my database is still active from your side. Now you will return that as cancelled and send few more active events. But i will not be sure which out of the active events is my rescheduled events because there may be events that user would have created private for him outside of my application

 

Hence it will be better if i can track if the new event is actually an event that is recheduled

 


Hey @Madan71582. While you won’t be able to track this from the event resource, you may have success tracking this from the invitee resource.

Check out our list event invitees endpoint which can be called for an event.

The invitee resource contains optional new_invitee and old_invitee fields which can be used to connect up a rescheduled event. When an invitee reschedules, the existing invitee will be canceled (and have rescheduled as true) and the new invitee’s URI will be in new_invitee. For the new event, the invitee will have an old_invitee, which will be the original invitee’s URI.

I hope this will allow you to sort this data in your system.