Managing Available Webhook URLs

How to add and edit a webhook URL in the Webhooks integration. User Roles required to access these settings: Account Owner or IT Support.

To send data to a third-party application using webhooks, you first need to add the application’s webhook URL into WhosOnLocation and configure the settings for sending the data.

Webhooks List

To add or edit webhooks in your integration, go to the list of webhooks.

  1. Go to Tools > Account.
  2. Select Integrations from the left-hand menu.
  3. Select the Webhooks integration.
  4. Click Settings.


Click Create a New Webhook to add, click View next to an existing webhooks to edit, or click Remove next to an existing webhook to delete.

Adding a Webhook

There are three sections when adding a webhook, Webhook Settings, Optional Settings, and Trigger Settings. Only Webhook Settings are required to add a webhook.


Fill in as many of these details as required and click Save to create your webhook.

Webhook Settings

These settings identify where data is being sent, the format it is in, and what happens when it arrives.


Webhook Name – used to easily identify the webhook.

Webhook URL – the unique web address of your third-party application that will receive the data.

Method – Desired action to be performed on the URL, select either POST or GET.

POST will send information to the application.
GET will ping the application telling it to do something but won’t include any information from WhosOnLocation.

Content Type – This is how the information is formatted when sent and is dictated by your third-party application. Select from Form Encoded, JSON, XML, or RAW. Where your application allows, we recommend using the JSON format.

Optional Settings

These are additional security settings which may be required by your third-party application. If required, you can enter these security settings here.


Basic Auth Username – Username required to satisfy your security settings.

Basic Auth Password – Password required to satisfy your security settings.

HTTP Headers – Information which will always be included in the URL that is receiving the data. This is generally used as an extra security measure by applications. Click the + button to add more.

Trigger Settings

Add static placeholders to create data sent to your webhook when using a custom data packet in your trigger settings. This allows you to use one value across many triggers which is easily modified in these settings.

Any placeholders added here can be used in a custom data packet when this webhook is selected. Click the + button to add more.


Enter the name of the trigger placeholder without spaces, e.g. ACS_Username. When using the placeholder in your custom data packet, enter it as {{webhook.PlaceholderName}}, e.g. {{webhook.ACS_Username}}.

Enter the value that will be sent when this placeholder is used, e.g. Admin.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request