Authentication
API access uses per-account credentials scoped to your own deployment — there's no shared, multi-tenant API surface to authenticate against.
Everything the UI shows — findings, assets, scan results, attack paths — is backed by a REST API running inside your own deployment, so automation and CI/CD pipelines can read the same data a person sees.
Early access note: the full endpoint-by-endpoint reference and OpenAPI spec are still being finalized for public publication. If you need to integrate against the API today, our team provides working examples and credentials directly as part of onboarding — request API access rather than waiting on this page.
API access uses per-account credentials scoped to your own deployment — there's no shared, multi-tenant API surface to authenticate against.
The API mirrors the UI's own data model: findings, assets, scans, integrations and attack-path/correlation results, each addressable on its own.
Responses are JSON, with pagination on list endpoints, matching what a typical modern REST API looks like.
The same API that powers the UI is what CI/CD gates, ticketing automation and custom reporting call against — not a separate, limited integration layer.