Skip to content
Developer Resources

How to Use Webhook.site to Troubleshoot your API Requests

Learn how to use Webhook.site to capture, inspect, and troubleshoot API and webhook requests when debugging GHL Customer Care integrations.

2 min read554 words6 explained imagesUpdated Wed, 4 Feb at 8:07 AM
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. What is Webhook.site
  2. How It Works
  3. Step 1: Visit Webhook.site
  4. Step2. Click on "Copy to clipboard" next to your unique Testing Webhook on the homepage
  5. Step 3. Go to Your Custom Integration, like Zapier or other third-party solution
  6. Step4. Replace the GHL Customer Care API URL with the Webhook.site testing URL
  7. Step5. Save your updates
  8. Step 6. Review Payload Data
  9. Step 7. Click Copy

Webhook.site is a free third-party tool that lets you inspect and capture the raw HTTP requests sent from integrations, workflows, or custom API calls. Using Webhook.site makes it easy to debug webhook payloads, verify configuration, and troubleshoot issues before sending payloads to GHL Customer Care or your production endpoints.


Video 1 Open in a new tab

TABLE OF CONTENTS


What is Webhook.site

Webhook.site instantly generates a unique test URL that collects all incoming webhook requests and displays them in real time. This makes it ideal for:

  • Capturing raw webhook payloads (headers, body, method)

  • Validating the structure of requests before sending them to your live endpoint

  • Troubleshooting integrations from Zapier, Make (Integromat), custom apps, or other automation tools 

IMPORTANT: The steps in this article are for Advanced Integration and for informational purposes only.While we do not currently support or service either the Basic or Advanced API due to their complexity, we have many tools and groups to help you get started and connected! For assistance with APIs, you can join our Developer Council Slack Community here: https://ghlcustomercare.com/dev-slack
We also hold a Developer Council Zoom Call once a month (second to last Friday) which you can find on the Events calendar here: https://ghlcustomercare.com/events

For more information and links to our API documentation, visit our developer's website:https://marketplace.https://ghlcustomercare.com/docs/

How It Works

Step 1: Visit Webhook.site


Open https://webhook.site in your browser. A unique test URL will be generated automatically.

Step 1: Visit Webhook.site (image 1 of 6) What this shows Open https://webhook.site in your browser. What this shows Illustrates the "Step 1: Visit Webhook.site" section of "How to Use Webhook.site to Troubleshoot your API Requests". This screenshot appears in the "Step 1: Visit Webhook.site" section of "How to Use Webhook.site to Troubleshoot your API Requests". The text alongside this image reads: Open https://webhook.site in your browser. A unique test URL will be generated automatically. Immediately after, the guide continues: For this example, we are using Zapier, and to use Webook.site to test you will need to click "Set Up Action.". Image 1 of 6 Where to goOpen https://webhook.site in your browser. A unique test URL will be generated automatically. Next stepFor this example, we are using Zapier, and to use Webook.site to test you will need to click "Set Up Action."

Step2. Click on "Copy to clipboard" next to your unique Testing Webhook on the homepage

Step2. Click on "Copy to clipboard" next to your unique Testing Webhook on the homepage (image 2 of 6) What this shows Open https://webhook.site in your browser. What this shows Illustrates the "Step2. Click on "Copy to clipboard" next to your unique Testing Webhook on the homepage" section of "How to Use Webhook.site to Troubleshoot your API Requests". This screenshot appears in the "Step2. Click on "Copy to clipboard" next to your unique Testing Webhook on the homepage" section of "How to Use Webhook.site to Troubleshoot your API Requests". The text alongside this image reads: Open https://webhook.site in your browser. A unique test URL will be generated automatically. Immediately after, the guide continues: For this example, we are using Zapier, and to use Webook.site to test you will need to click "Set Up Action.". Image 2 of 6 Where to goOpen https://webhook.site in your browser. A unique test URL will be generated automatically. Next stepFor this example, we are using Zapier, and to use Webook.site to test you will need to click "Set Up Action."

Step 3. Go to Your Custom Integration, like Zapier or other third-party solution

For this example, we are using Zapier, and to use Webook.site to test you will need to click "Set Up Action." 

Step 3. Go to Your Custom Integration, like Zapier or other third-party solution (image 3 of 6) What this shows For this example, we are using Zapier, and to use Webook.site to test you will need to click "Set Up Action." What this shows Illustrates the "Step 3. Go to Your Custom Integration, like Zapier or other third-party solution" section of "How to Use Webhook.site to Troubleshoot your API Requests". This screenshot appears in the "Step 3. Go to Your Custom Integration, like Zapier or other third-party solution" section of "How to Use Webhook.site to Troubleshoot your API Requests". The text alongside this image reads: For this example, we are using Zapier, and to use Webook.site to test you will need to click "Set Up Action.". Immediately after, the guide continues: Temporarily swap out the GHL Customer Care API URL for the Webhook.site URL for testing purposes. You'll follow a similar process for any other custom integration that is POSTING data into GHL Customer Care. Image 3 of 6 What to clickFor this example, we are using Zapier, and to use Webook.site to test you will need to click "Set Up Action." Next stepTemporarily swap out the GHL Customer Care API URL for the Webhook.site URL for testing purposes. You'll follow a similar process for any other custom integration that is POSTING data into GHL Customer Care.

Step4. Replace the GHL Customer Care API URL with the Webhook.site testing URL

Temporarily swap out the GHL Customer Care API URL for the Webhook.site URL for testing purposes. You'll follow a similar process for any other custom integration that is POSTING data into GHL Customer Care. 

Step4. Replace the GHL Customer Care API URL with the Webhook.site testing URL (image 4 of 6) What this shows Temporarily swap out the GHL Customer Care API URL for the Webhook.site URL for testing purposes. What this shows Illustrates the "Step4. Replace the GHL Customer Care API URL with the Webhook.site testing URL" section of "How to Use Webhook.site to Troubleshoot your API Requests". This screenshot appears in the "Step4. Replace the GHL Customer Care API URL with the Webhook.site testing URL" section of "How to Use Webhook.site to Troubleshoot your API Requests". The text alongside this image reads: Temporarily swap out the GHL Customer Care API URL for the Webhook.site URL for testing purposes. You'll follow a similar process for any other custom integration that is POSTING data into GHL Customer Care. Immediately after, the guide continues: Make sure to save your changes, then run whatever flow you have in place that would normally execute the webhook. If your tool or integration (like Zapier, Integromat, etc.) has a built-in testing tool, don't utilize this. Instead, use a…. Image 4 of 6 What this coversTemporarily swap out the GHL Customer Care API URL for the Webhook.site URL for testing purposes. You'll follow a similar process for any other custom integration that is POSTING data into GHL Customer Care. Next stepMake sure to save your changes, then run whatever flow you have in place that would normally execute the webhook. If your tool or integration (like Zapier, Integromat, etc.) has a built-in testing tool, don't utilize this. Instead, use a real-world example. If the webhook is triggered when a form is submitted, go to the form and submit a test. If the automation fires when an action is performed in an external system, perform said action. This will provide you and your developers with the most accurate information, and will be incredibly valuable when troubleshooting advanced API-related issues.

Step5. Save your updates

Make sure to save your changes, then run whatever flow you have in place that would normally execute the webhook. If your tool or integration (like Zapier, Integromat, etc.) has a built-in testing tool, don't utilize this. Instead, use a real-world example. If the webhook is triggered when a form is submitted, go to the form and submit a test. If the automation fires when an action is performed in an external system, perform said action.
This will provide you and your developers with the most accurate information, and will be incredibly valuable when troubleshooting advanced API-related issues.

Step 6. Review Payload Data

Next, you'll be presented with the raw data being received by GHL Customer Care anytime the webhook is executed. You can compare this with the information available on our API documentation websites to test your configuration. 

Step 6. Review Payload Data (image 5 of 6) What this shows Make sure to save your changes, then run whatever flow you have in place that would normally execute the webhook. What this shows Illustrates the "Step 6. Review Payload Data" section of "How to Use Webhook.site to Troubleshoot your API Requests". This screenshot appears in the "Step 6. Review Payload Data" section of "How to Use Webhook.site to Troubleshoot your API Requests". The text alongside this image reads: Make sure to save your changes, then run whatever flow you have in place that would normally execute the webhook. If your tool or integration (like Zapier, Integromat, etc.) has a built-in testing tool, don't utilize this. Instead, use a real-world example. If the webhook is triggered when a form…. Immediately after, the guide continues: Step 7. Click Copy Click Copy in the Upper Right of the Raw Data input box to copy the entire Payload. Save this for troubleshooting with your developers, or with the GHL Customer Care team. Image 5 of 6 What to fill inMake sure to save your changes, then run whatever flow you have in place that would normally execute the webhook. If your tool or integration (like Zapier, Integromat, etc.) has a built-in testing tool, don't utilize this. Instead, use a real-world example. If the webhook is triggered when a form is submitted, go to the form and submit a test. If the automation fires when an action is performed in an external system, perform said action. This will provide you and your developers with the most accurate information, and will be incredibly valuable when troubleshooting advanced API-related issues.
Buttons and menus referenced Step 6.Step 7.
Next stepStep 7. Click Copy Click Copy in the Upper Right of the Raw Data input box to copy the entire Payload. Save this for troubleshooting with your developers, or with the GHL Customer Care team.

Step 7. Click Copy

Click Copy in the Upper Right of the Raw Data input box to copy the entire Payload. Save this for troubleshooting with your developers, or with the GHL Customer Care team.

Step 7. Click Copy (image 6 of 6) What this shows Step 6. What this shows Illustrates the "Step 7. Click Copy" section of "How to Use Webhook.site to Troubleshoot your API Requests". This screenshot appears in the "Step 7. Click Copy" section of "How to Use Webhook.site to Troubleshoot your API Requests". The text alongside this image reads: Step 6. Review Payload Data Next, you'll be presented with the raw data being received by GHL Customer Care anytime the webhook is executed. You can compare this with the information available on our API documentation websites to test your configuration. Image 6 of 6 What this coversStep 6. Review Payload Data Next, you'll be presented with the raw data being received by GHL Customer Care anytime the webhook is executed. You can compare this with the information available on our API documentation websites to test your configuration.
Buttons and menus referenced Step 6.Step 7.

Was this guide helpful?

Related guides