The member list (GET /api/v2/members/list) and the member detail (GET /api/v2/members/{idMember}) now return the member's identification document in a new identification object.

Three read-only endpoints now expose the center's Rewards data: the current points balance of every member (GET /api/v2/rewards/members, paginated), the points history of a member (GET /api/v2/rewards/members/{idMember}/history) and a ranking of members by the points earned since a date, up to one year back (GET /api/v2/rewards/ranking).

Two payment webhooks are now available so your invoicing system can issue its credit notes: payment.refunded fires when a refund completes the refund of a payment, and payment.partially_refunded when a refund covers only part of it. Both carry the original payment in data plus a new data.refund block (idRefund, amount, lines, date). Every envelope now also includes version.

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.

The member_access.v2 webhook is now available. It fires when a member access is recorded and includes the access direction (accessForm: entrance / exit) and the authentication method (authenticationType: QR, card, facial recognition, manual…).

Every webhook event now has a dedicated reference page with its payload schema and a worked example. Start at How webhooks work for the envelope format and delivery semantics.

Activity schedule webhooks are now available: activity_schedule.created, activity_schedule.updated, activity_schedule.deleted and activity_schedule.canceled. Each delivery can carry up to 10 schedules in the data array.