> Calendly developer docs. For page Markdown, append .md to any URL.
> Index: https://developer.calendly.com/llms.txt
> API catalog: https://developer.calendly.com/.well-known/api-catalog
> OpenAPI: https://developer.calendly.com/openapi/calendly-api.yaml
> OAuth authorization server: https://calendly.com/.well-known/oauth-authorization-server
> MCP protected resource: https://mcp.calendly.com/.well-known/oauth-protected-resource
> Scheduling MCP endpoint: https://mcp.calendly.com
> Docs search MCP: https://developer.calendly.com/_mcp/server

# Webhook Payloads for Rescheduled Events

## See how webhook payloads change when invitees reschedule events

When an invitee reschedules an event, both webhook events (`invitee.created` and `invitee.canceled`) will be triggered.

## Understanding the payloads

When you receive the payloads at your URL, take note of a few key differences between the payloads:

* the `invitee.canceled` webhook payload will contain the data for the event that was canceled and include the value of `true` on the **`rescheduled` key**. When `False` shows on the `rescheduled` key, this indicates the event has not been rescheduled and is solely a canceled event by an invitee.

![invitee.canceled payload for a rescheduled event](/_fern-img/534bb50e3fe70f707858080106e8205523f0a873ae5a2a3f1f8ff02c2206a214.webp)

* The `invitee.created` payload will contain the event data for the new event created from the reschedule. You'll notice the `status` of the event is now `active` since the invitee is attending this newly created event (the rescheduled event from the canceled event.)

![invitee.created payload for a rescheduled event](/_fern-img/a094a066710e6624f34a5da6c873d110a3ccf8209246cc75c724e2fd08270116.webp)

* Please note that you can reference the value for the new invitee URI and the old invitee URI in this payload

The old (`old_invitee`) and new (`new_invitee`) URI references are located on the `invitee` model, and not the event model since the reschedule is per invitee and not the per event.

When making a call for the invitee resource `/scheduled_events/{event_uuid}/invitees/{invitee_uuid}`, there is a key of `status` which will indicate if this is an active invitee.