Identity
Corporate sign-in and automatic user provisioning.
- OIDC
- OAuth2 introspection
- SCIM 2.0
Integrations and API
Versioned REST APIs, OpenAPI contract, structured errors, idempotency, scoped API keys, signed webhooks and asynchronous jobs connect Exploit2Impact to portals, GRC tools, assessment pipelines and managed services.
By category
Where an integration requires credentials or external setup, it is supported and configurable by the deployment.
Corporate sign-in and automatic user provisioning.
Scenario enrichment with public and reputation sources.
Alerts on critical events in the channels the team already uses.
Formats and channels to connect the platform to other systems.
Components for controlled, scalable deployments.
Additional narratives and recommendations, with a provider chosen by the deployment and human review.
API contract
The supported surface for new integrations is /api/v1. Breaking changes require a new major version and legacy routes remain temporarily available with deprecation headers.
Error responses keep the legacy error field and add a structured envelope with code and message. Clients must tolerate additive fields.
| Endpoint family | What it covers |
|---|---|
| Simulation | Single, batch, scenario comparison, sensitivity analysis, CSV and SSE streaming |
| Analysis | Monte Carlo, maturity, supply chain, prediction, recommendations and narrative reports |
| Remediation and compliance | Remediation, ROI, compliance indicators and PDF |
| Workspace | Simulation history, scenarios, assets and export |
| Identity and tenants | Authentication, sessions, 2FA, OIDC, API keys, users, tenants, SCIM |
| Operations | Jobs, artifacts, schedules, webhooks, notifications, audit, health and readiness |
Tell us which systems you want to connect Exploit2Impact to: we will explain how to proceed.