Edwin AI Webhook Integration
Last updated – 20 November, 2026
The Edwin AI Webhook enables ingestion of events from any third-party monitoring or observability platform using a flexible webhook integration. This enables Edwin AI to consolidate events from multiple sources for centralized visibility, intelligent correlation, and incident investigation.
Edwin AI accepts webhook payloads in a Common Event Format (CEF), providing a standardized structure for ingesting and processing events from different third-party platforms. Payloads include key event details such as the affected resource, alert name, severity, timestamp, and a link to the original alert. Additional enrichment data, such as site names and support team information, can also be included to provide greater context for event correlation and incident investigation.
CEF Field Mapping Structure
All CEF event files must include field mappings from third-party events to Edwin’s standardized fields using JSON Path expressions.
The following table describes the event fields in the CEF mappings block:
| Event Field Name | Description | Required |
event_ci | The host or monitored resource(For example, hostname, IP) | Yes |
event_object | The instance on the resource (For example, an “instance” in LogicMonitor) | Yes |
event_source | Source of the event (For example, splunk) | Yes |
event_name | Name describing the alert condition | Yes |
event_severity | Severity of the event (For example, critical, major, minor) | Yes |
event_description | Short summary of the alert | Yes |
event_details | Long description of the alert | Yes |
event_time | Timestamp of the event in UTC format | Yes—If not provided in the payload, Edwin automatically generates the current timestamp. |
event_id | Unique identifier. Must be a valid UUID value | Yes—If not provided in the payload, Edwin automatically generates a new UUID. |
event_domain | Tenant ID or Customer ID (multi-tenant use cases) | No |
*_link fields | URLs pointing to the resource or event in the source system (for example, event_source_id_link) | No |
You can define fallback paths using multiple JSONPath strings. The first valid match is used.
Requirements for Configuring an Edwin AI Webhook
To configure a webhook for Edwin AI, you need the following:
- The URL address of your Edwin AI environment.
- An Edwin AI Client ID and Client Secret generated for the
event_writescope. - The CEF event information you want to send to Edwin AI.
Configuring Third Party Platforms to Send an Edwin AI Webhook
Disclaimer: The following steps provide the steps to send a webhook payload to Edwin AI from a third party. The payload templates and information provided may vary based on the platform used.
- Navigate to the webhook configuration settings in a third party platform.
For more information, see product documentation from the platform provider. - Create a Refresh Token payload to request an authentication token from Edwin AI.
For example, use the following payload template:
curl --location 'https://<Edwin_Url>.dexda.ai/auth/token' \
--data-urlencode 'client_id=<Edwin_Client_Id>' \
--data-urlencode 'client_secret=<Edwin_Client_Secret>' \
--data-urlencode 'grant_type=client_credentials'- Send the Refresh Token request payload from the third-party platform.
- Wait for a response from Edwin AI.
The response uses the following format:
{
"access_token": "<Auth_Token",
"issued_token_type": "urn:ietf:params:oauth:token-type:access_token",
"token_type": "Bearer",
"expires_in": 1799,
"expires_at": 1794002860909,
"now": 1794001061001
}- Save the
accessTokenvalue to use when sending events.
Note: You must request a new authentication token when the current token expires, as indicated by the expiresAt value.
- Create a CEF Event webhook payload with required mapped fields to send to the
/integration/event/v1endpoint.
For more information, see CEF Field Mapping Structure. - Include your authentication token in the
Authorizationheader, preceded byBearer.The following example payload contains the event’scefobject and anenrichmentsobject.
curl --location 'https://<EDWIN_URL>/integration/event/v1' \
--header 'Authorization: Bearer <AUTH_TOKEN>' \
--header 'Content-Type: application/json' \
--data '[
{
"cef": {
"eventCi": "https://google.com",
"eventObject": "testApp - Scheduled - HTTP Server",
"eventName": "alert-sch",
"eventDescription": "Total Time ≥ 1 ms",
"eventDetails": "Total Time: 275 ms - Suppressed",
"eventSeverity": 1,
"eventTimestamp": 1733840340000,
"eventSource": "Google",
"sourceRecord":
{"source_record_payload":
"sample"},
"class": "event",
"version": "1.1",
"eventDomain": ""
},
"enrichments": {}
}
]'- Wait for a response from Edwin AI.
A successful request returns an HTTP 200 status code in the following format:
[
{
"eventId": "ed7b5011-dfde-11ef-b600-4b494126bd19",
"acceptedStatus": true
}
]Edwin AI now receives events from the third-party platform. The eventId in the response payload identifies the event, and acceptedStatus: true indicates that the event was accepted.


