You can view responses by using this endpoint on any webhook events, whether you have registered or not. By default, the last 5 results will show, in descending “updated_at” order. This ensures the most recent objects created that match that webhook type, are the first listed in the response.

Webhook payloads can be large because we often include related data (example, the new_install event includes the customer object). Since the related schema can vary tremendously between records, this tool may be helpful for development purposes.

NOTE: When you receive the payload of an actual webhook event, it will only contain the object for which the event was triggered, and it will not be in an array as it will be depicted here.