Overview
Webhooks allows Ghost to send POST requests to user-configured URLs in order to send them a notification about it. The request body is a JSON object containing data about the triggered event, and the end result could be something as simple as a Slack notification or as complex as a total redeployment of a site.Setting up a webhook
Configuring webhooks can be done through the Ghost Admin user interface underSettings > Advanced > Integrations > Add custom integration. The only required fields to setup a new webhook are a trigger event and target URL to notify. This target URL is your application URL, the endpoint where the POST request will be sent. Of course, this URL must be reachable from the Internet.
If the server responds with 2xx HTTP response, the delivery is considered successful. Anything else is considered a failure of some kind, and anything returned in the body of the response will be discarded.
Available events
Currently Ghost has support for below events on which webhook can be setup:
Member events include the member’s custom field values in
metafields, in the same format as the Admin API. For member.added and member.edited, they’re in current. When an edit changes them, the values from before the edit are in previous.metafields. For member.deleted, the member’s values are in previous.metafields.
Stripe webhooks
Webhooks allow Ghost to communicate with Stripe. In order to use Stripe with a local version of Ghost you’ll need to do some additional setup to allow webhook events happen between Stripe and Ghost. First, follow the instructions on how to install and log into the Stripe CLI tool in the Stripe documentation. Then, before starting a local instance of Ghost, run the following command in your CLI. Note that the localhost port number should match the one used in your local Ghost install:whsec_. This secret needs to be given to Ghost on start up. In a new CLI window run the following:

