Findings API
List confirmed findings, severity, evidence status, affected asset, remediation state, and compliance mappings.
Pentoma's minimum API and webhook surface is focused on status, findings, exports, and developer handoff. The goal is workflow credibility without overbuilding a full developer platform before launch.
Minimum launch surface
Pentoma does not need every enterprise API on day one. It does need reliable exports, clear status, webhook events, and GitHub-ready remediation context for Pentoma Code.
List confirmed findings, severity, evidence status, affected asset, remediation state, and compliance mappings.
Export executive, engineering, and compliance-ready reports as HTML, PDF, JSON, or CSV.
Expose queued, running, validating, paused, cancelled, delivered, and retest lifecycle states.
Send HMAC-signed events for assessment.started, finding.confirmed, report.ready, assessment.paused, and assessment.cancelled.
Deliver line-level finding context into GitHub pull requests so remediation happens where engineers already work.
Webhook events
Webhooks are designed to integrate with compliance automation platforms like Drata and other GRC tooling your team uses, alongside Slack, Jira, GitHub, internal dashboards, or CI release checks.
assessment.started
An authorized assessment has begun running against the agreed scope.
finding.confirmed
A finding has passed reviewer validation and is ready for customer action.
report.ready
The customer-facing report package is ready for export or secure sharing.
assessment.paused
An active assessment has been paused — by customer request, scope change, or operator stop path.
assessment.cancelled
An assessment has been cancelled before completion and will not produce a report.
API objects
The launch API should prioritize assessment and finding records over broad configuration APIs.