API Docs

Authentication

• Send the API key in header X-Api-Key.
• The company is resolved automatically from the key (no company-id header required).
• Keys are shown once when created. Rotate by creating a new key and revoking the old one.

Endpoints

Create customer (JSON)

Required: type. Recommended: externalId.

curl -X POST "$API_BASE/api/public/customers" \
  -H "X-Api-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "externalId": "crm-123",
    "type": "Individual",
    "fullName": "Jane Doe",
    "email": "jane@example.com",
    "country": "US",
    "dateOfBirth": "1990-01-01",
    "isPep": false,
    "customFieldValues": [
      { "fieldDefinitionId": "GUID", "value": "Example" }
    ]
  }'

{ "customerId": "GUID", "documentIds": [] }

Create customer (multipart + documents)

• Include customer (JSON string) in the form body.
• If you upload files, also include documentsMeta as a JSON array with the same length and order as the files.

curl -X POST "$API_BASE/api/public/customers" \
  -H "X-Api-Key: YOUR_KEY" \
  -F "customer={\"externalId\":\"crm-123\",\"type\":\"Individual\",\"fullName\":\"Jane Doe\"}" \
  -F "documentsMeta=[{\"documentTypeId\":\"GUID\",\"documentCategoryId\":null}]" \
  -F "file=@passport.jpg"

{ "customerId": "GUID", "documentIds": ["GUID"] }

Create customer from images (AI)

Upload 1–2 images. The API runs AI extraction and creates the customer + stores a document.

curl -X POST "$API_BASE/api/public/customers/ai-create" \
  -H "X-Api-Key: YOUR_KEY" \
  -F "files=@front.jpg" \
  -F "files=@back.jpg"

Request requirements

• Required: type
• If type = Business: businessName is required.
• If type = Individual: fullName is required.
• Recommended: externalId (lets you safely retry without duplicates).

Create customer (JSON) — full field reference

customFieldValues[] item — field reference

documentsMeta[] item — field reference (multipart documents)

AI create response — extracted fields

The AI endpoint returns analysis.fields where each value is a string (or null).

Public Transactions API

Ingest transactions with participant snapshots. Complii resolves/matches customers, stores the transaction + snapshot, and calculates a transaction risk summary. Screening is executed using the selected Screening Preset (or the default preset marked as "Incoming Tx Default").

curl -X POST "$API_BASE/api/public/transactions" \
  -H "X-Api-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "externalTransactionId": "CM-00012345",
    "createdAtUtc": "2025-12-16T18:20:00Z",
    "transactionType": "REMITTANCE",
    "status": "COMPLETED",
    "amount": 250.00,
    "currency": "USD",
    "screeningPresetId": "GUID (optional)",
    "originCountry": "US",
    "destinationCountry": "CO",
    "participants": [
      { "role": "SENDER", "customerType": "INDIVIDUAL", "externalCustomerId": "CM-CUST-7788", "fullName": "Carlos Mendoza", "country": "US" },
      { "role": "BENEFICIARY", "customerType": "INDIVIDUAL", "fullName": "Maria Perez", "country": "CO" }
    ]
  }'

{ "transactionId": "GUID", "externalTransactionId": "CM-00012345", "participantCustomerIds": ["GUID","GUID"], "riskScore": 30, "riskLevel": "Medium", "screeningRunId": "GUID", "screeningPresetIdUsed": "GUID", "screeningTotalMatches": 0, "screeningSuspectAlerts": 0, "participants": [{ "role": "SENDER", "customerId": "GUID", "universalCustomerIdentityId": "GUID", "customerStatus": "Exists", "matchMethod": "ExternalId" }] }

Transaction (top-level) — full field reference

attachments[] item — field reference

participants[] item — field reference

participant documents (identificationDocuments[] / businessDocuments[] / files[]) — field reference