Otherwise, you end up in a descending vortex of madness trying to specify some protocol whereby the client can specify in advance which properties they care about.
Webhook payloads need to be logically monotonic[0]; this probably means either:
- having a lamport-clock timestamp for each payload so you can entirely discard older payloads in favour of new ones
- a well defined / consistent "merge" function over the subset of the payload you care about (e.g. maybe you know a customer's state can never go back from "registered" to "guest")
Sometimes you want to ignore webhooks based on the payload (or put them into a different queue). It's faster to do that if you get the payload up front.