Integrations
GET /integrations
Lists the tenant's configured integrations (type, status, last sync, findings count).
POST /integrations
Registers/updates an integration (upsert).
Body:
{
"type": "MICROSOFT_365",
"name": "Tenant M365 produção",
"config": {},
"credentials": {}
}
type (IntegrationType) supports: JIRA, SLACK, TEAMS, AWS, AZURE, GCP, QUALYS, TENABLE, CROWDSTRIKE, OKTA, AZURE_AD, WAZUH, ETERSCAN, PROWLER, GLPI, OPENCTI, GOOGLE_WORKSPACE, GITHUB, MICROSOFT_365, CNCS, SERVICENOW, ASANA, AUTHENTIK, FLEET, BACKUP_REPORT. The FLEET type (Fleet MDM, device source for the IT module) has its own card in Settings → Integrations and is synced by integrations-sync. This generic endpoint is how Microsoft 365/Azure AD, GCP, Google Workspace, AWS, Azure, Okta, GitHub and CNCS are connected; there are no dedicated per-vendor REST endpoints beyond the cases below.
ENTRA_PROVISIONING is not accepted by this endpoint. Microsoft 365 in write mode (JML) can only be configured through its own card in Settings → Integrations (it validates permissions, requires an administrator and is audited). A POST with type = ENTRA_PROVISIONING returns 400 (Tipo não permitido pela API).
GET authentication: API key or browser session. With a session (used by the control tests form) the response does not include config (URLs and options of each integration); with an API key it does. POST still requires an API key.
POST /integrations/:id/sync
Forces a sync of an integration. In this version it only supports integrations of type WAZUH (returns 400 for any other type). Rate limit: 5 syncs/min.
POST /integrations/wazuh/findings · GET /integrations/wazuh/findings
Ingestion (POST) and query (GET) of Wazuh-SCA-Bot findings. Different authentication: headers x-etershield-key (the Wazuh integration secret) + x-tenant-id, not x-api-key. The request is rejected if the secret is not configured.
Body strictly validated: 400 with field-level detail on an invalid payload:
resultaccepts"passed","failed","not_applicable"(underscore: the normalized form sent by the real producer) and"not applicable"(with a space)synced_ataccepts an ISO datetime with an offset (+00:00), not justZfindingsis an array: empty is valid. It means the policy no longer has failures and drives the automatic resolution of old findings; an empty array never causes a400- Only findings with CRITICAL or HIGH severity generate a Risk record: a single Risk per agent × policy pair, never one Risk per individual failed check
POST /integrations/wazuh/incidents
Creates an incident from a Wazuh alert (rule level ≥ 12). Authentication: tenant API key (x-api-key or Bearer). Unlike findings, agents and alert-rollups, it does not use x-etershield-key. Rate limit: 60 req/min per tenant.
POST /integrations/suricata/ingest
Ingestion of Suricata IDS EVE JSON events. Authentication via x-etershield-key (the Suricata ingestion secret) + x-tenant-id. CRITICAL alerts (C2/malware/trojan) automatically escalate to an Incident.
POST /integrations/jira/webhook · POST /integrations/opencti/sync · POST /integrations/prowler/findings · GET/POST/DELETE /integrations/slack · GET/POST/DELETE /integrations/teams · POST /integrations/eterscan/findings
Vendor-specific integration endpoints (Jira, OpenCTI, Prowler, Slack, Teams, EterScan). Authentication by API key, with two exceptions: slack and teams require a browser session (configuration is done in the dashboard) and jira/webhook requires x-api-key + x-tenant-id (and, if a webhook secret is configured, the HMAC signature). The remaining Wazuh ingestion endpoints (agents, alert-rollups) and POST /wazuh/enroll are in the index at the end.