Skip to main content

Chargify Webhooks

This guide covers how to use ngrok to integrate your localhost app with Chargify by using Webhooks. Chargify webhooks can be used to notify an external application whenever specific events occur in your Chargify account.

By integrating ngrok with Chargify, you can:

  • Develop and test Chargify webhooks locally, eliminating the time in deploying your development code to a public environment and setting it up in HTTPS.
  • Inspect and troubleshoot requests from Chargify in real-time via the inspection UI and API.
  • Modify and Replay Chargify Webhook requests with a single click and without spending time reproducing events manually in your Chargify account.
  • Secure your app with Chargify validation provided by ngrok. Invalid requests are blocked by ngrok before reaching your app.

Step 1: Start your app

For this tutorial, we'll use the sample NodeJS app available on GitHub.

To install this sample, run the following commands in a terminal:

git clone
cd ngrok-webhook-nodejs-sample
npm install

This will get the project installed locally.

Now you can launch the app by running the following command:

npm start

The app runs by default on port 3000.

You can validate that the app is up and running by visiting http://localhost:3000. The application logs request headers and body in the terminal and responds with a message in the browser.

Step 2: Launch ngrok

Once your app is running successfully on localhost, let's get it on the internet securely using ngrok!

  1. If you're not an ngrok user yet, just sign up for ngrok for free.

  2. Download the ngrok agent.

  3. Go to the ngrok dashboard and copy your Authtoken.
    Tip: The ngrok agent uses the auth token to log into your account when you start a tunnel.

  4. Start ngrok by running the following command:

    ngrok http 3000
  5. ngrok will display a URL where your localhost application is exposed to the internet (copy this URL for use with Chargify). ngrok agent running

Step 3: Integrate Chargify

To register a webhook on your Chargify account follow the instructions below:

  1. Access Chargify and sign in using your Chargify account.

  2. On the home page, select a site from the Site dropdown on the top of the page.

  3. On the site page, click Config, click Settings, and then click Webhooks.

  4. On the Webhooks page, click Add New Endpoint.

  5. On the Add New Endpoint page, enter the URL provided by the ngrok agent to expose your application to the internet in the Webhook URL field (i.e. URL to Publish

  6. Select the Events you want to subscribe this webhook. For this tutorial, select all.

  7. Click Add.

Run Webhooks with Chargify and ngrok

Chargify sends different request body contents depending on the event that is being triggered. Follow the instructions below to test connectivity between Chargify and your local application using the webhook you created.

  1. Access your Chargfy's site home page, click Tools on the left menu and then click Webhook Testing.

  2. On the Webhook Testing page, select one of the events you subscribed the webhook, select the webhook, and then click Send.

    Confirm your localhost app receives the create-project event notification and logs both headers and body in the terminal.

Optionally, you can verify the log of the webhook call in Chargify:

  1. On the left menu, click Tools and then click Webhook Panel.

  2. On the Webhooks page, click Details to see details of the webhook call. Webhook Logs

Inspecting requests

When you launch the ngrok agent on your local machine, you can see two links:

  • The URL to your app (it ends with for free accounts or for paid accounts when not using custom domains)
  • A local URL for the Web Interface (a.k.a Request Inspector).

The Request Inspector shows all the requests made through your ngrok tunnel to your localhost app. When you click on a request, you can see details of both the request and the response.

Seeing requests is an excellent way of validating the data sent to and retrieved by your app via the ngrok tunnel. That alone can save you some time dissecting and logging HTTP request and response headers, methods, bodies, and response codes within your app just to confirm you are getting what you expect.

To inspect Chargify's webhooks call, launch the ngrok web interface (i.e., and then click one of the requests sent by Chargify.

From the results, review the response body, header, and other details:

ngrok Request Inspector

Replaying requests

The ngrok Request Inspector provides a replay function that you can use to test your code without the need to trigger new events from Chargify. To replay a request:

  1. In the ngrok inspection interface (i.e. http://localhost:4040), select a request from Chargify.

  2. Click Replay to execute the same request to your application or select Replay with modifications to modify the content of the original request before sending the request.

  3. If you choose to Replay with modifications, you can modify any content from the original request. For example, you can modify the id field inside the body of the request.

  4. Click Replay.

Verify that your local application receives the request and logs the corresponding information to the terminal.

Secure webhook requests

The ngrok signature webhook verification feature allows ngrok to assert that requests from your Chargify webhook are the only traffic allowed to make calls to your localhost app.

Note: This ngrok feature is limited to 500 validations per month on free ngrok accounts. For unlimited, upgrade to Pro or Enterprise.

This is a quick step to add extra protection to your application.

  1. Access your Chargfy's site home page and click Edit current Site from the Site dropdown menu on top of the page.

  2. On the Site page, copy the value of the Site Shared Key.

  3. Restart your ngrok agent by running the command, replacing {your site shared key} with the value you have copied before:

    ngrok http 3000 --verify-webhook chargify --verify-webhook-secret {your site shared key}
  4. Access the Webhook Testing page and send a new test notification to your webhook.

Verify that your local application receives the request and logs information to the terminal.