New events — activity_booking.*

Two new activity booking webhooks are available: activity_booking.validated, sent when a member's attendance to an activity is validated, and activity_booking.canceled, sent when a booking is canceled. Both are configured under Activities and send one delivery per booking.

activity_booking.canceled fires on every cancellation, not only on validated bookings: use dateAttended to tell them apart — a value means the attendance had already been notified and whatever you granted should be reverted, null means the booking was never validated. Note that a mass cancellation (deleting a schedule or an activity) produces one delivery per affected booking.

Both events share the same member and activity_schedule objects used by the rest of the catalog. As part of this change, the member object in payment.succeeded now also carries its id; the component is named Member in the reference (it was PaymentMember), and no field was removed or renamed in the payload.

See Activity booking validated and Activity booking canceled for the full payloads.