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.

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.
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

    • Custom Dashboard Performance and Current Status widgets — Monitors and their supported child entities

      Your Custom Dashboard's Performance and Current Status widgets support the following set of child entities for the below set of monitor types. Performance Widget: Monitor Type Child Entity Web Transaction (Browser) Step URL Web Transaction Step URL ...
    • Limitations of custom instrumentation in .NET agent

      While most of the functions can be instrumented using custom instrumentation, the following kinds of methods will be ignored for profiling: 1. Constructors 2. Object finalizers and Disposer methods 3. Lambda functions 4. Property getter / setter 
    • Associate a device template to my network monitor

      In cases where even after successfully adding a network monitor, a device is discovered as unknown, a device template can be added and associated with that network device. Both Default and Custom Templates can be associated with the network devices. ...
    • Build custom Linux plugins

      Plugins are a great way to measure customized attributes and keep track of the data that matters the most. You can set thresholds to individual attributes and choose to get alerted if the set values exceed. Please follow the below steps to configure ...
    • Publish service status via custom domain

      Status page lets you share the current status of your services with your customers and end users. To publish public service status via custom domain, please perform the following steps: Create a new domain using which you can publish your service ...