Notification destinations

A Notification Destination tells Dockt how to deliver notifications to an external system. Each destination belongs to one Workspace and can be reused by several event routes.

Dockt separates the delivery target from event selection:

• A Notification Destination stores the delivery type, configuration, status, and delivery health.
• A Notification Route maps one event type to up to 20 Notification Destinations.

This separation lets you change a destination without editing every event route that uses it.

Destination types

Every destination has a type and a matching configuration object. Dockt supports the webhook type, which sends signed HTTPS requests to a configured URL. Creation returns its signing secret once, and explicit rotation returns the replacement secret once.

{
  "label": "Production events",
  "type": "webhook",
  "webhook": {
    "url": "https://example.com/webhooks/dockt"
  }
}

Fields such as id, label, status, and delivery belong to the Notification Destination. Transport-specific fields belong under the object named by type.

Event routes

A Notification Route selects destinations for one supported event type. The same destination can receive several event types, and one event type can deliver to several destinations.

Dockt supports these routed event types:

• assessment.completed
• assessment.reassessed
• document.completed
• document.failed

Routes contain destination IDs, not copied URLs or secrets. Updating a destination therefore affects every route that refers to it.

Destination lifecycle

New destinations are active. Disabling a destination keeps its route references but suppresses delivery until you activate it again. You must remove every route reference before deleting a destination.

Delivery health

Each destination includes a delivery summary with its latest event type, outcome, attempt time, and successful-delivery time. These fields are null before the first delivery attempt.

Use the Notification Destinations reference for exact routing and delivery behavior. To configure the webhook type, follow Receive webhooks.