Skip to main content
Every Business Verification (KYB) session a Business has run stays permanently linked to the Business entity. You can retrieve the full history, inspect each session’s registry data and AML hits, trigger re-verification, and generate PDF reports for audits.

​
Listing all Business Verification (KYB) sessions for a business

Filter the Sessions list by vendor_data: 
curl -G https://verification.didit.me/v3/sessions \
  -H "x-api-key: YOUR_API_KEY" \
  --data-urlencode "vendor_data=biz-acme" \
  --data-urlencode "page_size=50"
Response includes every Business Verification (KYB) session (regardless of status).

​
Understanding KYB features

Business entities track features independently:
FeatureWhat it covers
kyb_registryCompany registry lookup — existence, status, identity cross-check
kyb_company_amlCompany-level AML screening (sanctions, adverse media, watchlists)
kyb_documentsDocument collection and OCR cross-referencing
kyb_key_peopleOfficers, UBOs, beneficial owners — identification and optional KYC
The features map on the business entity reflects the latest status of each: 
"features": {
  "kyb_registry": "APPROVED",
  "kyb_company_aml": "APPROVED",
  "kyb_documents": "APPROVED",
  "kyb_key_people": "IN_REVIEW"
}
See KYB feature statuses for the full reference.

​
Inspecting a single Business Verification (KYB) session

curl https://verification.didit.me/v3/session/{session_id}/decision/ \
  -H "x-api-key: YOUR_API_KEY"
The KYB decision includes:
  • Company registry data (legal name, registration, status, incorporation date, addresses)
  • Officers and UBOs extracted from the registry
  • Ownership structure (cap table, beneficial ownership percentages)
  • Company AML results (hits, scores)
  • Per-person AML for each UBO and officer
  • Document results with OCR extracts
  • Decision reason codes
See KYB response schema for the full payload.

​
Triggering re-verification

Annual re-KYB, trigger-based re-checks, or remediation flows all start with a new session: 
curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "wf_kyb_annual",
    "vendor_data": "biz-acme"
  }'
The new session attaches to the existing Business entity and updates the features map on completion.

​
Resubmission vs new Business Verification (KYB) session

ScenarioUse
Registry lookup needs a corrected company nameResubmit — analyst edits data and re-runs registry
Additional document requested from the businessResubmit — business uploads the missing document
Annual or trigger-based re-KYBCreate a new session

​
Exporting a KYB report

Generate a comprehensive PDF for any Business Verification (KYB) session: 
curl https://verification.didit.me/v3/session/{session_id}/generate-pdf \
  -H "x-api-key: YOUR_API_KEY" \
  -o kyb-report.pdf
The PDF includes registry data, ownership structure, AML hits, document images, officer KYC status, and a cover page with decision reason.

​
Sharing a Business Verification (KYB) session

For consortium or partner workflows:
  • POST /v3/session/{session_id}/share/ — generate a shareable token.
  • POST /v3/session/import-shared/ — import on the receiving side.

​
Ongoing monitoring

Business entities in ongoing monitoring mode get periodic AML rescans. When a new sanctions or adverse media hit is detected, the business’s kyb_company_aml feature is updated and a business.data.updated webhook fires. Configure ongoing monitoring in the console at Workflows → [KYB workflow] → AML → Ongoing monitoring.

​
Next steps

KYB overview

How Business Verification (KYB) sessions work end-to-end.

KYB response

Full decision payload reference.

Key people

Officers, UBOs, and linked Users.