Every backend service serves interactive Swagger UI at /docs directly, and a merged OpenAPI spec is generated into docs/api/openapi.yaml in the platform repository.
All requests route through the API Gateway. Authentication is a Bearer JWT (Authorization: Bearer <token>) on every route except registration, login, password recovery, and the public billing catalogue.
/api/v1/auth, /api/v1/usersRegistration, login, MFA, self-service profile & password management.
/api/v1/billingPlans, checkout, subscriptions, invoices, webhooks.
/api/v1/engagements, /api/v1/scansEngagement lifecycle, scan dispatch, findings.
/api/v1/assets, /api/v1/findingsAsset registry, scheduled scanning, compliance reports.
/api/v1/socEvent ingestion, correlation, tenant-scoped alerting.
/api/v1/threatsIOC management, Threat DNA profiling.
/api/v1/dfirCase management, evidence, timeline.
/api/v1/easmDomain verification, discovery, exposure tracking.
/api/v1/basAttack simulation scenarios and results.
/api/v1/mobileSelf-declared checklist scans, dynamic lab sessions.
/api/v1/chat, /api/v1/copilotAI assistant and SOC analyst copilot.