Thin events now include field changes on related objectsPublic preview
What’s new
Thin events now include a before-and-after representation of what changed on the related object. The changes field contains two optional sub-fields:
before: The previous values of the fields that changedafter: The new values of the fields that changed
Only modified fields are included in the before and after objects, allowing you to identify exactly what changed without needing to compare full object representations.
In this release, the following event types support the changes field:
- v2.core.account.closed
- v2.core.account.created
- v2.core.account.updated
- v2.core.account[configuration.customer].capability_status_updated
- v2.core.account[configuration.merchant].capability_status_updated
- v2.core.account[configuration.recipient].capability_status_updated
- v2.core.account[configuration.storer].capability_status_updated
- v2.core.account[defaults].updated
- v2.money_management.outbound_payment.updated
- v2.money_management.outbound_transfer.updated
- v2.money_management.payout_method.updated
Impact
The changes field simplifies webhook processing by providing an immediate view of what changed on an object. Instead of storing previous object states or comparing full objects to identify changes, you can now directly inspect the before and after values.
This is particularly useful for:
- Building audit logs that track specific field changes
- Triggering conditional logic based on which fields were modified
- Debugging webhook events by quickly understanding what triggered the event