Ketryx Documentation
Book a DemoFAQTraining Videos
  • Introduction
  • 📄Manuals
    • MAN-01 Ketryx Lifecycle Management
    • MAN-02 Software Release Process
    • MAN-03 Supply Chain Management: Software Dependencies
      • Threat Modeling
      • Vulnerability Management
      • Working with CycloneDX
      • Working with SPDX
    • MAN-04 Supply Chain Management: Cloud Dependencies
    • MAN-05 Milestones
    • MAN-06 Test Management
    • MAN-07 Traceability
    • MAN-08 Risk Management
    • MAN-09 Git-Based Configuration Items
    • MAN-10 Managing items in Ketryx
    • MAN-11 Approval Rules
    • MAN-12 Computational Controls
    • MAN-13 Data Export
  • 🛠️Work Instructions
    • WI-01 Requirement
    • WI-02 Software Item Specification
    • WI-03 Task
    • WI-04 Test Case
    • WI-05 Test Execution
    • WI-06 Anomaly
    • WI-07 Complaint
    • WI-08 Change Request
    • WI-09 Corrective and Preventive Action (CAPA)
    • WI-10 Risk
    • WI-11 Document
  • 🌐Integrations
    • Jira
    • Azure DevOps
    • TestRail
    • Jama
    • Polarion
    • Chrome extension
    • Source Code
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Code Change Reviews
    • Release documents
      • Google Workspace
    • Authentication
  • 📚Reference
    • Ketryx Query Language
    • Advanced Settings
    • Glob Pattern Matching Algorithm
    • Traceability Configuration
    • Document Templating
    • Project Settings
    • Custom Item Types
    • Assistant
    • Agents
    • Release Notes
  • 🔃API
    • Authentication
    • Build API
    • Project API
    • Item API
    • Webhooks
Powered by GitBook

Ketryx

  • ketryx.com
  • What is Ketryx?

Resources

  • FAQ
  • Training Videos

© 2025 Ketryx Corporation

On this page

Was this helpful?

Export as PDF
  1. API

Webhooks

Webhooks to receive API notifications upon certain events in Ketryx

PreviousItem API

Last updated 6 months ago

Was this helpful?

Webhooks can be used to receive programmatic notifications upon certain events in Ketryx.

Webhooks are configured via the advanced setting . The following events are supported:

  • recordApproval: Approval of an item record

  • releaseApproval: Approval of a version/release

  • milestoneApproval: Approval of a milestone

  • documentApproval: Approval of a document in the EDMS

  • testPlanApproval: Approval of a release test plan

  • vulnerabilityApproval: Approval of a vulnerability

Each event can be configured to trigger a webhook call via an HTTP POST or GET request. When using a POST request (the default), a JSON payload will be sent with the request, containing the following data:

Event
Fields in JSON payload

recordApproval

userId, itemId, recordId, isControlled, newRecordId

documentApproval

userId, itemId, recordId, isControlled, newRecordId

vulnerabilityApproval

userId, itemId, recordId, isControlled, newRecordId

releaseApproval

userId, versionId, isReleased, releaseDate

milestoneApproval

userId, milestoneId, isFullyApproved

testPlanApproval

userId, versionId, testPlanId

All IDs are specified as Ketryx ID strings (e.g., KXREC1N91YGN3JB8PVT4DDFVF4Y64YT).

Note that webhooks are also triggered for partial approvals, i.e., any time a user makes an approval, even if the approved object is not fully approved yet. To distinguish fully approved objects, use fields such as isControlled, isReleased, and isFullyApproved. If the approval resulted in a new (controlled) record, that record will be indicated by the field newRecordId.

Webhooks are delivered asynchronously. The result of webhook calls can be inspected in a project's History > System logs.

🔃
Webhooks