Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.

This version of GitHub Enterprise was discontinued on 2023-03-15. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Testing webhooks

Review your webhook deliveries on GitHub, including the HTTP Request and payload as well as the response.

Now that you've configured your local server, you might be interested in pushing your code to the limits. To that end, GitHub's webhooks view provides some tooling for testing your deployed payloads.

Listing recent deliveries

Every webhook has its own "Recent Deliveries" section, which lists, at a glance whether a delivery was successful (green check) or failed (red x). You can also identify when each delivery was attempted.

GitHub Enterprise Server keeps a log of each webhook delivery for 8 days.

Screenshot of the "Recent Deliveries" tab on the "Manage webhook" page.

Digging into results

By expanding an individual delivery, you'll be able to witness precisely what information GitHub is attempting to send to your server. This includes both the HTTP Request and Response.


The webhook delivery view provides information on which Headers were sent by GitHub. It also includes details about the JSON payload.

Screenshot of the "Request" tab of a webhook delivery, including the "Headers" and "Payload" sections.


The response tab lists how your server replied once it received the payload from GitHub. This includes the status code, the headers, and any additional data within the response body.

Screenshot of the "Response" tab of a webhook delivery, including the "Headers" and "Body" sections.