API reference, webhook payloads, integration guides.
For developers integrating CyberTwin with Jira, ServiceNow, Slack, Teams, or building against the public API. Open documentation, no signup required.
- (01)
Public API
Documents what ships today — the read API (posture, findings, compliance scores, risk acceptances) on the Operate plan and above, outbound webhooks, HMAC-SHA256 signing, retry behaviour, and the public /api/health endpoint.
/docs/api - (02)
Webhook payloads
Two events ship today: finding.created and finding.remediated. HMAC-SHA256 signed, exponential-backoff retry, dead-letter replay from settings.
/docs/api#webhooks Native delivery, no relay: add a Slack or Teams endpoint in webhook settings, paste the channel’s incoming-webhook URL, and events arrive as formatted channel messages. About 2 minutes per channel.
/docs/slack-teamsLive read-only pulls (identity, cloud, network platforms) are on the post-launch roadmap. Today the engine reads the config exports you upload; outbound webhooks are what ship.
/docs/api#webhooksHow the recommendation engine works. ALE calculation chain, compliance scoring math, attack-path heuristics, catalog freshness policy. The same document an auditor reviewing your assessment would want.
/methodologyEvery number we cite, sourced + dated — the breach/risk benchmarks behind the math, and the per-vendor catalog price provenance, in one place.
/docs/sources
Found a docs gap? Email feedback@cybertwin.io. We respond to every documentation request and prioritize gaps that block real integration work.