# Audit Log Webhook By creating a webhook for [audit log](/docs/audits-and-reports/audit-log.md) notifications, you can gather all notifications into a single platform. *** ### Prerequisite
ItemDescription
Apono PremiumApono plan providing the most features and dedicated account support
*** ### Configure a webhook Follow these steps to configure a webhook: 1. On the [**Webhooks**](https://app.apono.io/webhooks) page, click **Add Webhook**. The **Add Webhook** page appears. 2. Click **Audit Webhook**. 3. Enter a unique, alphanumeric, user-friendly **Audit Webhook Name** for identifying this webhook. 4. Click the **Status** toggle to **Active**. 5. From the **Type** dropdown menu, select **HTTP Webhook**. 6. From the **Method** dropdown menu, select a REST method. 7. In the **URL** field, enter the URL of the target system that will receive the webhook. {% hint style="warning" %} The webhook URL **must adhere** to the following requirements: * Uses the HTTPS protocol * Does **not** specify any custom ports {% endhint %} 8. In the **Body Template** field, construct a JSON body for the webhook payload. The following is an example webhook payload. ```json { "event_type": "{{event_type}}", "event_time": "{{event_time}}", "data": { "timestamp": "{{data.timestamp}}", "action": "{{data.action}}", "actor_id": "{{data.actor_id}}", "actor_name": "{{data.actor_name}}", "actor_type": "{{data.actor_type}}", "source": "{{data.source}}", "target_id": "{{data.target_id}}", "target_type": "{{data.target_type}}", "target_name": "{{data.target_name}}", "metadata": "{{data.metadata}}", "current_target_object": "{{data.current_target_object}}", "previous_target_object": "{{data.previous_target_object}}" } } ``` {% hint style="success" %} Click **View audit event's payload schema** to reveal the base payload schema and available data fields. You can also refer to the [Audit Log Webhook Payload Schema Reference](/docs/webhook-integrations/webhook-payload-references/audit-log-webhook-payload-schema-reference.md) to read the descriptions of each data field. {% endhint %} 9. Choose the relevant authentication method and enter the information required by the target system. {% tabs %} {% tab title="None" %} From the **Authentication Type** dropdown menu, select **None**. {% endtab %} {% tab title="OAuth" %} Follow these steps to add OAuth authentication: 1. From the **Authentication Type** dropdown menu, select **OAuth**. The OAuth settings appear. 2. Define the OAuth settings.
SettingDescription
Client IDUnique identifier assigned by the authorization server
Client SecretSecret key issued by the authorization server
Token Endpoint URLURL 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
{% endtab %} {% tab title="Bearer Token" %} Follow this step to add Bearer Token authentication: 1. From the **Authentication Type** dropdown menu, select **Bearer Token**. The Bearer token settings appear. 2. Enter the **Token**. {% hint style="success" icon="lightbulb" %} By default the password is not shown. To display the token, click (eye icon). {% endhint %} {% endtab %} {% tab title="Custom" %} Follow these steps to add custom authentication: 1. Under **Headers**, use the **Key** and **Value** fields to set the credential information. 2. If your tool or service has several values, enter each key-value pair in a separate row. {% hint style="info" %} The following table uses [Datadog](/docs/webhook-integrations/request-webhook/logs-and-siems/datadog.md) as an example. {% endhint %} | Key | Value | | -------------------- | ------------ | | *DD-API-KEY* | *\* | | *DD-APPLICATION-KEY* | *\* | | {% endtab %} | | | {% endtabs %} | | 10. (Optional) In the **Timeout in seconds** field, enter the duration in seconds to wait before marking the request as failed. 11. (Optional) Define **Response Validators** to verify that the response from the webhook meets specified criteria: 1. Click **+ Add**. A row of settings appears. 2. Starting with *$.data.*, enter the **Json Path** of the JSON parameter. 3. In the **Expected Values** field, enter a value and press the Enter key on your keyboard. 4. Repeat step **c** to add several expected values. 5. Repeat steps **a-d** to add multiple response validators. 12. 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. {% hint style="success" %} 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 [troubleshoot your webhook](/docs/webhook-integrations/troubleshoot-a-webhook.md). {% endhint %} 13. Click **Save Webhook**. The new webhook appears in the **Webhooks** table. Active webhooks are preceded by a green dot. Inactive webhooks are preceded by a white dot. Apono audit log notifications will be sent to the target system each time an [audit log](/docs/audits-and-reports/audit-log.md) event occurs. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apono.io/docs/webhook-integrations/audit-log-webhook.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.