Webhook integration

What are Incident Parameters and Custom Parameters?

Incident parameters and Custom parameters get passed along with the body of the URL during an HTTP request invocation. Incident parameters are pre-defined system parameters that get passed in the body of the invoked URL. The incident parameters are substituted with the actual value of your specified monitor in the HTTP response. Incident parameters can be used in Invoke URL Actions in IT Automation, and to customize Message Titles in Third-Party Integrations. Below are all the Incident Parameters that are defined by Site24x7:


The $INCIDENT_DETAILS parameter is available only for RBL monitors.

  1. The $MSP_CUSTOMER_NAME parameter will be only accessible to MSP users. Similarly, $BU_NAME parameter will be only shown to Business Units users. The parameter can be used for setting up third-party integrations for different MSP and Business Units customers.
  2. $MONITOR_DASHBOARD_LINK is not available for MSP admins or users.

Custom Parameters can be defined and passed along with your URL during an HTTP request. You can pass them as a Param name=value pair, wherein you can use Global Parameters to substitute it with a Constant or Dynamic value of your choice. You can utilize Custom Parameters for specific use cases like creating flexible notification pop up in your third party service portal. Custom Parameters will be passed in a JSON, in the same format as specified by you during the HTTP request. You can specify a Custom Parameter in two different ways:

Custom Parameters syntax when specified in JSON format:




Custom Parameters syntax when specified as key-value:




    • Related Articles

    • Difference between a website monitor and a SOAP Web Service monitor

      Website monitor will support monitoring of any web application via POST, GET and HEAD methods of configuration. Learn more on the performance metrics provided for a website monitor. SOAP Web Service monitors , on the other hand, lets you to ...

    • Setting up a website monitor w.r.t content match and HTTP configuration

      Regarding the website defacement (content match) configuration, you can set keyword checks to find the existence and non-existence of keywords in your HTML response. As far as the HTTP configurations are concerned, we support HEAD, GET, and POST ...

    • Troubleshoot the Error 404 and Error 99 for RabbitMQ

      When installing the RabbitMQ plugin, you may encounter the following errors: HTTP Error 404: Not Found: This error usually occurs when Site24x7's RabbitMQ monitoring plugin attempts to access the /api/overview page of RabbitMQ, but the resource ...

    • Exclude Site24x7 monitoring traffic from Google Analytics

      You can exclude traffic from the Site24x7 Web Transaction (Browser) monitor and Webpage Speed (Browser) traffic from Google Analytics in two ways. To exclude traffic for the Web Defacement monitor, you can follow the first method. 1. Creating a ...