Skip to main content

Scanning API

Use these endpoints to trigger repository static analysis and cloud infrastructure scans. Use the X-CLOUDGENI-API-KEY header for all examples here.

Repository Static Analysis

Create a Checkov-backed static analysis run for a repository:
Fetch the current active analysis for the repository:
Fetch findings for a specific analysis:

Repository IaC Scans

Create an IaC repository scan:
Use this when you want the repository scan flow exposed by the iac-scans routes rather than the Checkov-only static analysis flow.

Cloud Infra Scans

Create a cloud scan against an existing cloud integration:
The analysisEngine segment is part of the route. Supported values include:
  • prowler-ocsf
  • aws-security-hub
  • azure-defender
You can also pass optional cloud-scan fields such as credentialId and regions when the route supports them.

Cloud Scan Findings

Fetch findings for a specific cloud scan:
You can filter, page, search, and sort cloud findings with query parameters such as:
  • limit
  • offset
  • search
  • severity
  • status
  • frameworks
  • summaryStatusCategories
  • resourceType
  • resourceId
  • sortBy
  • sortOrder
Array filters accept either repeated query parameters or comma-separated values. Framework filters match a finding when it has at least one mapping for any requested framework. Add includeSummary=true to return severity totals for the same filtered result set; summaryStatusCategories can further limit that summary to FAILED, SUPPRESSED, or PASSED. For example, this request returns open high- or critical-severity findings mapped to SOC 2 or ISO 27001:

CLI Equivalents

If you would rather not call raw HTTP:

Pipeline Setup

The API endpoints above are available for custom automation. For Cloudgeni-managed repository pipelines, use the IaC Pipeline Agent to create and test SCAN and VALIDATE workflows.