Testing Webhook Requests

You can test webhook requests using external tools or the built-in test function. The built-in test function also checks whether the server the request is being sent to uses TLS 1.2 (passed) or not (not passed).

Table of Contents

• To Test a Project-Specific Webhook Request
• To Test a Global Webhook Request
• To Test a Webhook Request Using RequestBin

To Test a Project-Specific Webhook Request

1. Select a project from the project list, then select the tab.api.title tab.
2. Press to add new, or double-click on an already existing request.
3. Press webhookTest.button.label.
4. If the request is processed successfully, you receive a 200 OK popup message. If the request is unsuccessful, you will receive a 404 Not found popup message.

Note: Messages are in JSON format.

To Test a Global Webhook Request

1. From the VCC Live menu, select call_center.menu.label > settings.menu.label, then select the tab.api.title tab.
2. Press to add new, or double-click on an already existing request.
3. Press webhookTest.button.label.
4. If the request is processed successfully, you receive a 200 OK popup message. If the request is unsuccessful, you will receive a 404 Not found popup message.

Note: Messages are in JSON format.

To Test a Webhook Request Using RequestBin

1. Visit http://requestb.in.
2. Press Create a RequestBin.
3. Copy the URL to your clipboard.
4. Paste the URL into URL textbox in the Webhook settings.
5. Make a phone call and set a disposition.
6. Check your bin at http://requestb.in to analyse the request.

Note: The last 20 requests are stored for 48 hours.