A webhook payload contains data about events occurring in a source system. Typically formatted as JSON, this structured information is sent to a specified URL when a predefined event triggers the webhook. Understanding the payload structure is essential for developers to process and respond to incoming webhook data effectively. This page outlines the standard format of our webhook payloads, detailing the key components in facilitating data exchange between applications.
The WebhookPayload
type is defined as follows:
cuid (string)
A unique identifier for the webhook request.
Example: "1736201637380-0"
event (WebhookEvent)
The type of event that triggered the webhook.
Example: "FindingPublished"
targetType (WebhookTarget)
The type of entity associated with the event.
Example: "finding"
targetCuid or targetCuids
The payload will include either targetCuid
or targetCuids
, but never both.
targetCuid (string): Used for single-entity events.
Example: "cm4wxq2ly000a0v79f9ky0um3"
targetCuids (string[]): Used for multi-entity events.
Example: ["cm4wxq2ly000a0v79f9ky0um3", "cm5lljwdv000adbcm0vak590c"]
When updating a single finding (targetCuid):
When bulk updating findings (targetCuids):