Developer

API-first screening infrastructure.

CCAI is designed for programmatic consumption. Platform teams integrate screening into existing workflows without adopting a standalone product.

CCAI is consumed as infrastructure: APIs for product systems, dashboard surfaces for operators, and one evidence contract underneath both.

API Endpoints

Authentication uses an API key. Tenant context is resolved from the key, and responses carry identifiers for audit correlation.

Method	Endpoint	Description
POST	/api/v1/lists/upload	Upload CSV or JSON entities and create a snapshot
POST	/api/v1/batches/run	Run screening against an uploaded snapshot
GET	/api/v1/batches/{batch_id}	Check batch status
GET	/api/v1/batches/{batch_id}/results	Retrieve per-entity screening results
GET	/api/v1/batches/{batch_id}/audit	Retrieve batch audit summary and evidence refs
GET	/api/v1/batches/{batch_id}/media-signals	Retrieve adverse-media signals when available
POST	/api/v1/review-cases/create-from-batch	Create review cases from flagged results

Webhook POST body

Product events are delivered as tenant-scoped JSON envelopes. Delivery attempts, retries, and dead-letter state are tracked internally.

{
  "event_type": "batch.completed",
  "tenant_id": "01969f8a-0d4f-74f4-a566-fb8c8d327002",
  "payload": {
    "batch_id": "0196a3f7-7e04-76f2-9ef5-4daef6caa019",
    "snapshot_id": "0196a3f7-24b8-7cf2-b35d-b78dcda743a1",
    "status": "completed",
    "record_count": 2,
    "error": ""
  }
}

API Samples

These examples use synthetic data and the product API routes documented in the engine.

POST/api/v1/lists/upload

Upload a screening list

Accepts a CSV file or JSON array and returns a tenant-scoped snapshot.

Request

curl -X POST https://api.corecomplianceai.com/api/v1/lists/upload \
  -H "X-API-Key: ccai_your_key" \
  -H "Content-Type: application/json" \
  -d '[
    {"name":"MV Northstar Trader","type":"VESSEL","id":"IMO 9123456","country":"MH"},
    {"name":"Blue Harbor Logistics LLC","type":"ORGANIZATION","country":"US"}
  ]'

Response

{
  "list_id": "0196a3f7-24b8-7a9e-8c9f-88ebc7b9639e",
  "snapshot_id": "0196a3f7-24b8-7cf2-b35d-b78dcda743a1",
  "record_count": 2,
  "status": "ingested"
}

POST/api/v1/batches/run

Run screening against the snapshot

Starts screening for a previously uploaded snapshot and returns correlation IDs.

Request

curl -X POST https://api.corecomplianceai.com/api/v1/batches/run \
  -H "X-API-Key: ccai_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "snapshot_id": "0196a3f7-24b8-7cf2-b35d-b78dcda743a1"
  }'

Response

{
  "batch_id": "0196a3f7-7e04-76f2-9ef5-4daef6caa019",
  "job_id": "job_0196a3f7_0001",
  "snapshot_id": "0196a3f7-24b8-7cf2-b35d-b78dcda743a1",
  "status": "queued"
}

GET/api/v1/batches/{batch_id}/audit

Retrieve the audit summary

Returns compact evidence navigation metadata for a completed batch.

Request

curl https://api.corecomplianceai.com/api/v1/batches/0196a3f7-7e04-76f2-9ef5-4daef6caa019/audit \
  -H "X-API-Key: ccai_your_key"

Response

{
  "batch_id": "0196a3f7-7e04-76f2-9ef5-4daef6caa019",
  "snapshot_id": "0196a3f7-24b8-7cf2-b35d-b78dcda743a1",
  "status": "completed",
  "record_count": 2,
  "result_count": 2,
  "decision_counts": {
    "CLEARED": 1,
    "REVIEW": 1
  },
  "layer_distribution": {
    "L1_DETERMINISTIC": 1,
    "L2_VECTOR": 1
  },
  "media_signal_count": 0,
  "evidence_refs": {
    "results": "/api/v1/batches/0196a3f7-7e04-76f2-9ef5-4daef6caa019/results",
    "media_signals": "/api/v1/batches/0196a3f7-7e04-76f2-9ef5-4daef6caa019/media-signals"
  },
  "regulatory_status": "SCREENING_SIGNAL",
  "generated_at": "2026-05-04T14:31:00+00:00"
}

Batch Screening

Batch processing is the primary operational mode for most integrations. Batches return durable identifiers that connect uploaded snapshots, screening jobs, results, and review cases.

1.Submit entity file (CSV, XLSX, JSON, Parquet) or JSON array
2.Receive batch_id and trace_id in the response
3.Poll for completion or receive webhook notification
4.Retrieve results with per-entity resolution detail
5.Export evidence bundles or audit reports as needed

Event and Webhook Model

CCAI emits events at key points in the screening lifecycle. Webhooks are delivered via HTTP POST with signed payloads. Events include trace_id and batch_id for correlation.

Event	Trigger
batch.completed	All entities in a batch have been resolved
batch.failed	Batch processing encountered an unrecoverable error
alert.created	A new case has been escalated to human review
monitoring.delta	A monitored entity’s status changed on re-screen

Evaluation Workspace

Before production integration, teams can evaluate CCAI in a sandboxed environment. Submit test batches against reference data, inspect resolution results and evidence output, and validate API integration patterns.

The evaluation workspace uses the same engine and protocol as production. The only difference is the data scope and access tier.

CCAI as a screening layer

CCAI is infrastructure, not a product you switch to. It fits into existing compliance architectures.

For platform teams

Embed screening as an API call within existing entity onboarding, transaction monitoring, or KYC workflows. CCAI handles resolution and evidence generation. Your platform handles the business logic.

For compliance systems

Feed CCAI the entity lists your existing systems produce. Consume the structured evidence output for regulatory reporting. CCAI does not replace your compliance program — it provides the screening execution and evidence layer.

For data pipelines

Submit batch files on a schedule. Receive structured results with full lineage. Load results into your data warehouse or reporting system. CCAI operates as a processing stage, not a destination.

Get API access.

Request integration credentials to test the API against your platform requirements.

Request API Access

Evidence

Decision packages, receipt binding, and regulatory audit exports.