Send integration failure notifications to your internal systems with event-triggered HTTP messages
An integration webhook delivers immediate notifications to your internal systems when an integration enters a Warning or Error state. This enables timely detection and response to issues, helping prevent downstream impact.
Follow these steps to configure an Apono webhook:
On the page, click Add Webhook. The Add Webhook page appears.
Click Integration.
Enter a unique, alphanumeric, user-friendly Integration Webhook Name for identifying this webhook.
Click the Status toggle to
The webhook URL must use the HTTPS protocol.
In the Body Template field, construct a JSON body for the webhook payload. The following is an example webhook payload.
Click View event's payload schema to reveal the payload schema and available data fields.
(Optional) If applicable, enter the authentication information required by the target system.
Under Filters, define one or several filters from the Integration, Type, and Status dropdown menus.
(Optional) In the Timeout in seconds field, enter the duration in seconds to wait before marking the request as failed.
(Optional) Define Response Validators to verify that the response from the webhook meets specified criteria:
Click + Add. A row of settings appears.
For more information about the test, click View Invocation Data. A panel opens revealing the request, response, and other relevant details.
Should your test fail, view these tips to .
Click Save Webhook.
The new webhook appears in the Webhooks table. Active webhooks are marked with a green dot. Inactive webhooks are marked with a white dot.
Apono notifications will be sent to your target system when the status of an integration has changed to a warning or error state.
From the Type dropdown menu, select HTTP Webhook.
From the Method dropdown menu, select the POST method.
For the URL field, enter the URL of the target system that will receive the webhook.
In the Expected Values field, enter a value and press the Enter key on your keyboard.
Repeat step c to add several expected values.
Repeat steps a-d to add multiple response validators.
Click Test to generate a test event to trigger your webhook. A Test successful or Test failed response status will appear at the bottom of the page. A successful test will send mock data to the target system.
Target System API
Authentication information used when making requests to the target system
Apono supports the following authentication:
Bearer Token
OAuth
Custom (key-value pairs passed in the header)
This is required only if the system receiving the webhook notifications requires authentication.
Target System Webhook URL
URL of the target system that will receive the webhook
{
"event_type": "{{event_type}}",
"event_time": "{{event_time}}",
"data": {
"id": "{{data.id}}",
"name": "{{data.name}}",
"type": "{{data.type}}",
"status": "{{data.status}}",
"issues": [
{
"status": "{{data.issues.status}}",
"message": "{{data.issues.message}}"
}
]
}
}Follow this step to add Bearer Token authentication:
Under Headers, use the Key and Value fields to set the access token.
Authorization
Bearer <API_TOKEN>
Follow these steps to add OAuth authentication:
From the Authentication Type dropdown menu, select OAuth. The OAuth settings appear.
Define the OAuth settings.
Follow these steps to add custom authentication:
Under Headers, use the Key and Value fields to set the credential information.
If your tool or service has several values, enter each key-value pair in a separate row.
DD-API-KEY
<API KEY>
DD-APPLICATION-KEY
<KEY ID>
Client ID
Unique identifier assigned by the authorization server
Client Secret
Secret key issued by the authorization server
Token Endpoint URL
URL where the authorization code or refresh token is exchanged for an access token
Scopes
(Optional) Set of permissions requested to access specific resources or APIs