Edwin AI Catchpoint Integration

Last updated - 17 December, 2025

The LogicMonitor Edwin AI Catchpoint Integration enables Edwin AI to receive alert events from your Catchpoint environment in real time using custom webhooks. This facilitates automated response, alert enrichment, and cross-platform incident correlation.

This integration supports structured JSON payloads using the Edwin Common Event Format (CEF) and can be customized using Catchpoint webhook macros to enrich event data with test metrics, rule metadata, and more.

Setting up the Edwin AI Catchpoint integration involves the following:

• Creating and configuring a webhook in Catchpoint
• Assigning webhooks to Catchpoint Alerts
• Using enrichments in webhook payloads for custom data

All setup actions are explicitly required, and Edwin AI cannot process data until configurations are completed.

Requirements for Configuring Edwin AI Catchpoint Integration

To configure your Edwin AI Catchpoint Integration, you need the following:

• Access to Alert Webhooks in your Catchpoint account
• An Edwin AI Client ID and Client Secret generated for event_write scopes
  For more information, see Edwin AI API Credential Management.

Configuring the Edwin AI Catchpoint Integration

1. Create a new webhook in Catchpoint. 
   For more information, see Alert Webhook Guide from Catchpoint. 

2. Configure your webhook settings using the following:

Field	Value
Name	LogicMonitor Edwin
URL	https://portalname.dexda.ai/integration/event/v1
Format	Edwin AI  Note: When you select “Edwin AI” the Edwin AI CEF webhook template auto-populates to streamline configuration.
On Failure Alert	Email

3. Add API request headers based on one of the following authentication methods:
   • To set up Basic Auth for your authentication method use the following code to format your Authorization header:
     Use your generated Client ID and Token. For more information, see Edwin AI API Credential Management.
     

     Basic base64(clientId:clientSecret)

     Copy
   • To set up OAuth 2 for you authentication method do the following:

1. Use the following API call to obtain the token:
   

   
   curl --location 'https://${orgId}.dexda.ai/auth/token' \
   --header 'Content-Type: application/x-www-form-urlencoded' \
   --data-urlencode 'client_id=${clientId}' \
   --data-urlencode 'client_secret=${clientSecret}' \
   --data-urlencode 'grant_type=client_credentials'

   Copy
   
   The response returns a JSON Web Token (JWT) that includes the access token and its expiration period.
   The following code displays an example:
   

   
   {
       "access_token": "**************",
       "issued_token_type": "urn:ietf:params:oauth:token-type:access_token",
       "token_type": "Bearer",
       "expires_in": 1799,
       "expires_at": 1765542339105,
       "now": 1765540539128
   }

   Copy

2. Use the following returned token to form your Authorization header:
   

   
   Authorization: Bearer ${access_token}

   Copy

4. (Optional) Define or customize your webhook payload.
   The built-in Edwin AI template works without needing any changes. 
   If you create a custom template, ensure the following:
   • You include all required fields for your webhook. 
     For more information, see Mapping Fields. 
   • You include the required timestamp field:
     

     "eventTimestamp": {{alert.firstSeen.epochMilli}}

     Copy
     For more information on customizing using alert webhook macros, see Alert Webhook Macro Index from Catchpoint. 

5. Save the webhook and assign the webhook to alerts.

6. (Optional) Create additional webhooks for custom routing.
   You can configure separate webhooks per severity or product group if different workflows are required.