Skip to main content
Sazabi sends one JSON envelope for every webhook delivery. The type value is the notification type that matched the endpoint subscription. Issue lifecycle events include the public issue resource, its component and event, linked artifacts, and the selected issue-event report.

Issue delivery

issue_triggered, issue_resolved, issue_ignored, issue_updated, issue_reopened, and issue_ongoing deliveries use this shape:
On issue_triggered, issue.agentPrompt carries the issue’s agent prompt (the GET /v1/issues/{issueId}/agent-prompt text) for your own coding agent; it is null on other events. On issue_updated, issue.event is the change itself (type updated) and notification.message says what changed: the severity went up, or it now affects another component. On issue_reopened, sent when a resolved or ignored issue is reopened by a person, Sazabi’s agent, or a synced tracker task, issue.event is the reopen (type updated, with the reopen’s note), notification.message says the issue was reopened and any other change made with it, and the envelope adds reopened: from (resolved or ignored), resolvedAt (when it was resolved or ignored, or null), and previousSlackPermalink (the issue’s Slack alert, or null). Until every subscription to issue_updated also names issue_reopened, a subscription to issue_updated receives issue_reopened too. On issue_ongoing, a reminder that the issue is still open, the envelope adds ongoing: the reminder’s step (0 to 6 are 1, 2, 3, 7, 14, 21 and 28 days after the issue opened, 7 and later are 2, 3, 4… months after), openedAt (when the issue was created or last reopened), and openFor (how long it has been open, such as "3 days"). issue.event is the issue’s newest event, since a reminder records none. The report is the issue event’s MDX document. It is redacted for common credential assignments and bounded to 80,000 UTF-8 bytes. If the report is truncated, report.reportTruncated is true. Artifact metadata is inline; use the artifact URL or GET /v1/artifacts/{artifactId}/download for content.

Signatures

Each request includes X-Sazabi-Webhook-Id, X-Sazabi-Delivery-Id, X-Sazabi-Event, and X-Sazabi-Signature. The signature value is t=<timestamp>,v1=<hex digest>; verify the HMAC-SHA256 digest over <timestamp>.<raw request body> with the endpoint signing secret before parsing JSON.