Zintegrity API · Early access

Zintegrity API

Integrate CMMC scoping, gap assessment and executive briefing generation into your own applications and client portals. The API returns the same reports produced by the Zintegrity platform.

Quickstart
# 1. Create a submission for a client's documentation
curl "$ZIN_API/v1/submissions" \
  -H "Authorization: Bearer $ZIN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Example Co.","external_id":"engagement-123"}'

# 2. Upload a folder as a ZIP archive
curl "$ZIN_API/v1/submissions/$SUBMISSION_ID/folder" \
  -H "Authorization: Bearer $ZIN_API_KEY" \
  -H "Content-Type: application/zip" \
  --data-binary @documents.zip

# 3. Request a CMMC Level 2 gap assessment
curl "$ZIN_API/v1/reports" \
  -H "Authorization: Bearer $ZIN_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: engagement-123-gap-v1" \
  -d '{"submission_id":"'$SUBMISSION_ID'","capability":"cmmc.l2.rev2.gap_analysis"}'

# 4. Check status, then download the workbook
curl "$ZIN_API/v1/reports/$REPORT_ID" -H "Authorization: Bearer $ZIN_API_KEY"
curl "$ZIN_API/v1/reports/$REPORT_ID/artifact" \
  -H "Authorization: Bearer $ZIN_API_KEY" -o gap-assessment.xlsx

Capabilities

Reports for CMMC Level 1 and Level 2

Each capability is available for both levels. Completed reports include the document and the structured JSON used to generate it.

Zintegrity API report capabilities
ReportCapabilityFormatScope
Executive briefingcmmc.{l1,l2}.rev2.executive_briefingPPTXTwelve-topic briefing, checked against the source documentation
Scoping reportcmmc.{l1,l2}.rev2.scopingDOCXBoundary, asset categorization, provider treatment, scoping issues
Gap assessmentcmmc.{l1,l2}.rev2.gap_analysisXLSXAll objectives, or a single control or domain

Limits: 50 MiB per file, 100 documents and 1 GiB per submission, and 256 MiB per ZIP upload. Reports run asynchronously; clients poll for status.

Integration

Designed for reliable integration

Checksum verification

Each upload is verified against its declared SHA-256 hash. Duplicate content is reused rather than reprocessed.

Sealed submissions

A submission is sealed when its first report is requested, so evidence cannot change during analysis.

Idempotent requests

Report requests accept an idempotency key, so retries after a lost response do not create duplicate reports.

Expiring API keys

Keys expire and are stored only as hashes. The full secret is displayed once at creation.

Folder uploads

Submit ZIP archives with subfolders. Unsupported, hidden and unsafe entries are listed in the response.

Usage reporting

Reports draw on prepaid units. Status checks and downloads are not charged, and failed analyses release their unit.

Request access to the Zintegrity API

The API is available in early access to MSPs, RPOs, assessors and compliance platforms. Describe your use case and our team will provision a project.