Webhook API

Webhook integrations allow your system to receive real-time notifications from Soda Cloud when certain events occur, such as check evaluations, incident changes, or contract updates.

Webhook integrations are available to organizations with a Soda license. Contact us to learn more.

Soda Cloud can push real-time events to any endpoint you control, so the moment a check fails, an incident moves, or a contract is published, the systems your team already lives in find out about it. Webhooks turn Soda Cloud into a source of structured, timely signal for the rest of your operational stack. Common patterns include:

• Pipe alerts into your on-call rotation, so failed checks open pages or tickets in PagerDuty, Opsgenie, or whatever tool your team is on.

• Drive automation: kick off remediation jobs, pause downstream pipelines, or trigger reruns when specific checks fail.

• Sync data quality events into your own observability stack, alongside your existing logs and metrics.

• Keep external systems of record in lockstep with Soda incidents and contract changes, so your catalog, ticketing tool, or governance platform reflects the latest state.

---

Scopes

Webhooks can be configured to listen for one or more event scopes:

Scope	Description
Alert Notifications	Triggered when a check result causes an alert (based on notification rules)
Incidents	Triggered when incidents are created or updated in Soda Cloud
Contracts	Triggered when a data contract is published (created or updated)

---

Event Types

Depending on the selected scope, one or more of the following event types will be sent to your endpoint:

Check Evaluation

Sent when a check evaluation triggers an alert. It carries the check's outcome and a link back to the result in Soda Cloud so a human can investigate further.

---

Incident Created

Sent when a new incident is opened, with enough context for a downstream system to create a corresponding ticket, channel, or page.

---

Incident Updated

Sent when an existing incident changes, so downstream systems can stay in sync as severity, status, or scope evolves.

---

Contract Published

Sent when a data contract is published or updated, useful for catalog sync, change auditing, or kicking off downstream validation.

---

You are not logged in to Soda and are viewing the default public documentation. Learn more about Documentation access & licensing.