CyberTwin
Documentation

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)THE INDEX
  1. (01)

    Public API

    Documents what ships today — outbound webhooks, HMAC-SHA256 signing, retry behaviour, and the public /api/health endpoint. The read API (findings, posture snapshots, reports) is on the roadmap.

    /docs/api
  2. (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
  3. (03)

    Slack and Teams relays

    A ~10-minute relay recipe: paste the snippet, configure the channel, and webhook events land in Slack or Teams. No webhook engineering required.

    /docs/slack-teams
  4. (04)

    Inbound integrations

    Live 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#webhooks
  5. (05)

    Engine methodology

    How 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.

    /methodology
  6. (06)

    Sources & provenance

    Every number we cite, sourced + dated — the breach/risk benchmarks behind the math, and the per-vendor catalog price provenance, in one place.

    /docs/sources
Docs feedback

Found a docs gap? Email feedback@cybertwin.io. We respond to every documentation request and prioritize gaps that block real integration work.