The absence of the id parameter from the organiser object in the Booking Cancelled webhook payload is due to its omission in the construction of the organiser object within the handleCancelBooking.ts file. Unlike the Booking Created and Booking Rescheduled webhooks, where the id is included, the code for handling booking cancellations does not explicitly include the id in the organiser object.

To address this inconsistency, you would need to modify the section of the code that constructs the organiser object for the Booking Cancelled webhook payload to include the id. This involves adjusting the payload construction in the handleCancelBooking.ts file, specifically where the organiser details are set for the webhook payload.

For reference, the current construction of the organiser object for cancellations does not account for the id, focusing instead on properties like email, name, timeZone, timeFormat, and language. This is why the id parameter is present in the payloads for created and rescheduled bookings but missing from the cancelled booking webhook payload.

If you're looking to make the organiser object consistent across all booking-related webhooks, adding the id to the payload for cancellations would be the necessary step. This change would ensure that the organiser object structure remains uniform across different types of booking webhooks, facilitating a more predictable and reliable data format for webhook consumers.

To continue the conversation, mention @dosu.

@alishaz-polymath @Shpadoinkle
Should we include the username in the organizer object as well?

@alishaz-polymath @Shpadoinkle Should we include the username in the organizer object as well?

Yes, that should be fine!