Skip to main content
Webhook notifications send JSON payloads to any HTTP endpoint when Validio detects data quality incidents, schema changes, or source errors. Use webhooks to integrate Validio alerts with custom tools, internal dashboards, or automation workflows that aren’t covered by the built-in notification channels. In Validio, you configure webhooks in two steps: create a Webhook integration that holds the endpoint URL and authentication header, then create one or more channels that route alerts through that integration.

Create a webhook integration

  1. In Validio, navigate to Workspace > Integrations and click + New integration.
  2. From the Integration type list, select Webhook.
  3. Enter a Name for the integration.
  4. Enter the Webhook URL of the HTTP endpoint that should receive payloads.
  5. (Optional) Enter an Authorization header value to include in requests to the endpoint.
  6. (Optional) Click Test integration to send a test payload and verify that the endpoint responds successfully.
  7. Click Create integration.

Create a webhook channel

  1. In Validio, navigate to Notifications > Channels and click + New channel.
  2. Under Integration, select the Webhook integration you created.
  3. Enter a Name for the channel.
  4. Select the Namespace where the channel will be created.
  5. Click Create.

Webhook configuration parameters

After creating the channel, add notification rules on the channel’s details page to control which incidents trigger webhook payloads.

Request timeout and retry behavior

There is no timeout for Validio webhook requests. Webhook endpoints should respond with an HTTP 2xx within 30 seconds; otherwise the request is treated as a failed attempt. Failed message requests are retried every 30 minutes, up to 20 times.

Webhook payload

Webhook payload is data embedded in a HTTP POST as JSON format. When your Notification rule is triggered, the webhook payload is sent to the specified HTTP endpoint. The payload structure varies depending on the notification type.
Notifications on Backfilled ValidatorsValidio does not send notifications for incidents when backfilling validators.

Validator incidents

Validator incidents occur when your data breaches a configured Threshold. The payload structure varies depending on Segmentation and Threshold type.
JSON (segmented validator, dynamic threshold)

Dynamic threshold

The payload structure for dynamic thresholds include the value, boundary, and decisionBoundsType: LOWER, UPPER, or UPPER_AND_LOWER.
JSON (Dynamic threshold, upper and lower bounds)
JSON (Dynamic threshold, lower bound)

Fixed threshold

The payload structure for fixed thresholds include the comparison value, value, and comparison operator: LESS, LESS_EQUAL, EQUAL, NOT_EQUAL, GREATER, or GREATER_EQUAL.
JSON (Fixed threshold, LESS operator)
JSON (Fixed threshold, LESS_EQUAL operator)

Difference threshold

The payload structure for difference thresholds include the difference_type which contains either ABSOLUTE or PERCENTAGE.
JSON (Difference threshold, PERCENTAGE type)

Schema changes

Validio can send notifications about changes in your schema. changeTypes can include one of the following: Nullability, MissingField, JtdType, or UnderlyingType.
JSON (Schema change)

Segment limits

JSON (Segment limit)

Source errors

JSON (Source error)