HTTP-JSON delivery methods
Define the delivery method
HTTP-JSON type delivery methods send alerts to any server configured to receive JSON objects. Alerts are encapsulated as a JSON object and sent using the POST request method over HTTP or HTTPS. If the destination server uses Digest access authentication, you can identify the user and password required for authentication.
Â
You can find below the information required on the New Delivery Method window for this delivery method (for the creation process visit Manage delivery methods).
Name | A unique name that identifies this specific delivery method. |
---|---|
Timezone | This is the time zone that will be used to calculate when alerts can be sent. This will be applied to the schedule defined in any sending policy that uses this delivery method. |
URL | The URL of the server to which the alerts should be sent. |
Language | The language in which to send the alert content. |
Content-Type |
|
Choose the desired authentication method | Choose one of the available authentication options:
|
Add headers | You may add specific headers to the JSON objects using this delivery method. To do it, check the Add headers box at the bottom of the window. Enter the required header names and values and click the Add button to include them in the delivery method. The list will all the headers added will appear below. Reserved header names Note that Content-Type, Content-Lenght, Accept, Authorization and Host are reserved headers and cannot be used as names. |
Activate the delivery method
The new method is saved in Pending status.
An HTTP test message with a code is sent to the URL specified in the delivery method. This activation code must be validated on the server side before the delivery method can be used. Click pending activation under the status column, paste the validation code into the Activation Code window and click Apply.
You can now associate this new delivery method with sending policies to start receiving alerts through this method.
Â