Notifications API - JSON models

The actual set of fields in the JSON model of a notification configuration depends on the type of the notification.

This page lists parameters and examples of JSON models for different notification types.

Ansible Tower notification

ParametersJSON example

The `NotificationConfig` object

Configuration of a notification. The actual set of fields depends on the type of the notification. See Notifications API - JSON models in Dynatrace Documentation for example models of every notification type.

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "ANSIBLETOWER",
  "id": "da08eb4e-29c2-4bf2-be24-7e424959e8ab",
  "name": "My AnsibleTower notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": true,
  "jobTemplateURL": "https://myDomain.compute.amazonaws.com/#/templates/job_template/10",
  "acceptAnyCertificate": true,
  "username": "jsmith",
  "password": null,
  "jobTemplateID": 10,
  "customMessage": "{ImpactedEntity} Problem {ProblemID}: {State}"
}

Email notification

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "EMAIL",
  "id": "9972ea44-1e51-4567-a10b-8687b0c6d92c",
  "name": "My email notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": true,
  "subject": "{State} Problem {ProblemID}: {ImpactedEntity}",
  "body": "{ProblemDetailsHTML}",
  "receivers": [
    "john.smith@company.com"
  ],
  "ccReceivers": [
    "james.brownh@company.com"
  ],
  "bccReceivers": [
    "james.brownh@company.com"
  ]
}

HipChat notification

HIPCHAT

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "HIPCHAT",
  "id": "ada688e4-216a-421e-91e6-76d1a56230c0",
  "name": "My HipChat notification",
  "alertingProfile": "4f5e00f4-39b3-455a-820b-3514843615f3",
  "active": true,
  "url": "https://my.hipch.at/v2/room/myID/notification?auth_token=abcd1234 ",
  "message": "Problem {ProblemID}: {ProblemTitle} \n\n {ProblemDetailsText}"
}

Jira notification

JIRA

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "JIRA",
  "id": "acbed0c4-4ef1-4303-991f-102510a69322",
  "name": "My Jira notification",
  "alertingProfile": "4f5e00f4-39b3-455a-820b-3514843615f3",
  "active": true,
  "username": "john.smith",
  "password": "",
  "url": "https://my-jira.atlassian.net/rest/api/2/",
  "projectKey": "DEV",
  "issueType": "Task",
  "summary": "Problem {ProblemID}: {ProblemTitle}",
  "description": "{ProblemDetailsText}\n"
}

Opsgenie notification

OPS_GENIE

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "OPS_GENIE",
  "id": "bc805303-4c7e-416e-80ca-aa0d9f608fd4",
  "name": "My Opsgenie notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": false,
  "apiKey": null,
  "domain": "api.opsgenie.com",
  "message": "{ProblemImpact} Problem {ProblemID}"
}

PagerDuty notification

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "PAGER_DUTY",
  "id": "993213e1-a77b-4c76-80aa-044e073fd1bb",
  "name": "My PagerDuty notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": true,
  "account": "myPagerDuty",
  "serviceApiKey": "9876zyxw",
  "serviceName": "myService"
}

ServiceNow notification

SERVICE_NOW

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "SERVICE_NOW",
  "id": "4e006117-6cb7-4eb5-a080-0ec96cc2fad0",
  "name": "My ServiceNow notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": false,
  "instanceName": "myServiceNowInstance",
  "url": null,
  "username": "john.smith",
  "password": null,
  "message": "{ProblemImpact} Problem {ProblemID}: {ProblemTitle}",
  "sendIncidents": true,
  "sendEvents": true
}

Slack notification

SLACK

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "SLACK",
  "id": "cebe8a38-ddfd-4062-aa9f-2f1a0562bd88",
  "name": "MySlack 1",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": false,
  "url": "https://hooks.slack.com/services/T000/B000/ZZZ",
  "channel": "@john.smith",
  "title": "Problem {ProblemID} is {State}: \n\n {ProblemDetailsText}"
}

Trello notification

TRELLO

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "TRELLO",
  "id": "b999e4ab-6293-486f-b083-5b5d737f5052",
  "name": "My Trello notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": false,
  "applicationKey": "",
  "authorizationToken": "",
  "boardId": "",
  "listId": "",
  "resolvedListId": "",
  "text": "Problem {ProblemID} is {State}",
  "description": "{ProblemDetailsMarkdown}"
}

VictorOps notification

VICTOROPS

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

json
{
  "type": "VICTOROPS",
  "id": "3e21c269-00d8-4cd2-a4d5-c53263f23f76",
  "name": "My VictorOps notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": false,
  "apiKey": null,
  "routingKey": "myTeam",
  "message": "Problem {ProblemID} - {ProblemTitle} is {State}"
}

Webhook notification

WEBHOOK

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

The `HttpHeader` object

The HTTP header.

Element Type Description Required

name

string

Element	Type	Description	Required
name	string	The name of the HTTP header.	required
value	string	The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the `null` value. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with the `null` value.	optional

The name of the HTTP header.

required

value

string

The value of the HTTP header. May contain an empty value.

Required when creating a new notification.

For the Authorization header, GET requests return the null value.

If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with the null value.

optional

json
{
  "type": "WEBHOOK",
  "id": "fbaf6757-2123-483a-a44e-3aac006128da",
  "name": "My custom notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": true,
  "url": "https://sample.free.beeceptor.com",
  "acceptAnyCertificate": false,
  "payload": "{\n\"State\":\"{State}\",\n\"ProblemID\":\"{ProblemID}\",\n\"ProblemTitle\":\"{ProblemTitle}\"\n}",
  "headers": [
    {
      "name": "Authorization",
      "value": null
    }
  ]
}

xMatters notification

XMATTERS

ParametersJSON example

The `NotificationConfig` object

Element	Type	Description	Required
id	string	The ID of the notification configuration.	optional
name	string	The name of the notification configuration.	required
alertingProfile	string	The ID of the associated alerting profile.	required
active	boolean	The configuration is enabled (`true`) or disabled (`false`).	required
type	string	Defines the actual set of fields depending on the value. See one of the following objects: `EMAIL` -> EmailNotificationConfig `PAGER_DUTY` -> PagerDutyNotificationConfig `WEBHOOK` -> WebHookNotificationConfig `SLACK` -> SlackNotificationConfig `HIPCHAT` -> HipChatNotificationConfig `VICTOROPS` -> VictorOpsNotificationConfig `SERVICE_NOW` -> ServiceNowNotificationConfig `XMATTERS` -> XMattersNotificationConfig `ANSIBLETOWER` -> AnsibleTowerNotificationConfig `OPS_GENIE` -> OpsGenieNotificationConfig `JIRA` -> JiraNotificationConfig `TRELLO` -> TrelloNotificationConfig The element can hold these values `ANSIBLETOWER` `EMAIL` `HIPCHAT` `JIRA` `OPS_GENIE` `PAGER_DUTY` `SERVICE_NOW` `SLACK` `TRELLO` `VICTOROPS` `WEBHOOK` `XMATTERS`	required

The `HttpHeader` object

The HTTP header.

Element Type Description Required

name

string

Element	Type	Description	Required
name	string	The name of the HTTP header.	required
value	string	The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the `null` value. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with the `null` value.	optional

The name of the HTTP header.

required

value

string

The value of the HTTP header. May contain an empty value.

Required when creating a new notification.

For the Authorization header, GET requests return the null value.

If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with the null value.

optional

json
{
  "type": "XMATTERS",
  "id": "07ced25a-dff4-4431-ab3a-571a5eab8562",
  "name": "My xMatters notification",
  "alertingProfile": "c21f969b-5f03-333d-83e0-4f8f136e7682",
  "active": false,
  "url": "https://acmecorp.xmatters.com/api/integration/1/functions/3744c145-47fd-9ab7/triggers",
  "acceptAnyCertificate": false,
  "headers": [
    {
      "name": "Authorization",
      "value": null
    }
  ],
  "payload": "{\n    \"impactedEntity\": \"{ImpactedEntity}\",\n    \"pid\": \"{PID}\",\n  \"problemId\": \"{ProblemID}\",\n  \"problemDetailsText\": \"{ProblemDetailsText}\",\n  \"problemImpact\": \"{ProblemImpact}\",\n    \"problemSeverity\": \"{ProblemSeverity}\",\n    \"problemTitle\": \"{ProblemTitle}\",\n   \"problemURL\": \"{ProblemURL}\",\n    \"state\": \"{State}\",\n    \"tags\": \"{Tags}\"\n}"
}

Notifications API - JSON models

Ansible Tower notification

The NotificationConfig object

Email notification

The NotificationConfig object

HipChat notification

The NotificationConfig object

Jira notification

The NotificationConfig object

Opsgenie notification

The NotificationConfig object

PagerDuty notification

The NotificationConfig object

ServiceNow notification

The NotificationConfig object

Slack notification

The NotificationConfig object

Trello notification

The NotificationConfig object

VictorOps notification

The NotificationConfig object

Webhook notification

The NotificationConfig object

The HttpHeader object

xMatters notification

The NotificationConfig object

The HttpHeader object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `NotificationConfig` object

The `HttpHeader` object

The `NotificationConfig` object

The `HttpHeader` object