Changelog
API ReferenceChangelogDashboard
Back to All

September 2026

2 months ago

In September, we released major features for Individual and Business verification APIs, including Reusable KYC for cross-account verification, Document results visibility for Individual applications, and multi-layer ownership traversal for enhanced Business checks.

2026-09-29 — Individual verification 2.2: Document results and API alignment

Aligned Individual OpenAPI and guides with document verification responses.

Added

  • Document results: documented documentType, merged ocr, and per-side ocrSides on application queries
  • Client Access Links: full CRUD endpoints at /v1/client-integration/links for managing access links
  • API reference coverage: Application and Profile metadata inputs now fully documented

Changed

  • Application responses: creation returns an acknowledgment with optional collection link; query returns status and step results without embedded Profile
  • Document & Face results: removed resultData wrapper for cleaner schema
  • Profile idDocs: now flat records with category: DOC | SELFIE; updates use upsert / remove operations
    • DOC replaces other records of the same type; SELFIE replaces other selfies
    • Each upsert replaces the whole record—resend fields to retain them
  • Profile fields: corrected verifiedInfo coverage; AML monitoring and auto-renew settings use ENABLED / DISABLED instead of booleans

Fixed

  • Request validation: corrected document type combinations and required fields
  • Query contracts: review answers may be null before conclusion; INACTIVE Profiles remain readable
  • Schema cleanup: removed unsupported Application resume and idempotency claims; Profile detail omits internal version and fileId
  • Documentation alignment: updated getting-started and webhook result-retrieval guidance

2026-09-02 — Business Registry Verification Pro: ownership traversal

Aligned Business OpenAPI with the maxLayer ownership traversal feature.

Added

  • maxLayer parameter on POST /v1/business/enhanced_checks
    • New BusinessEnhancedCheckRequest schema: BusinessCheckRequest + maxLayer
    • Optional integer 2-10, default 2 (subject company = layer 1)
    • Multi-layer traversal only takes effect when mode is HYBRID
    • Out-of-range values return 400 Bad Request
  • Layer tracking: layer and parentNode fields on OfficerInfo and ShareholderInfo
    • layer: entry's depth in ownership tree (subject = 1, register = 2)
    • parentNode: registration number of the company whose register the entry came from
    • Returned for single-layer checks too (where layer is always 2)

Changed

  • EnhancedCheckResult: documented asynchronous traversal response
    • Traversal check returns status IN_PROGRESS with only core fields until all layers resolve
    • Poll GET /v1/business/checks/{id} for the completed tree
  • Result aggregation: officersInfos / shareholdersInfos now contain flattened registers of every traversed company (not just subject's)
  • Beneficial owner calculation: with traversal, beneficial owners are individuals whose ownership multiplied along each chain and summed across chains reaches 25%+
  • Examples: updated request/response examples for single-layer and traversal scenarios

Fixed

  • HYBRID mode description: corrected fallback direction
    • HYBRID queries cached sources first, falls back to live official sources when no match found (not the other way)
    • Per RegistryVendorChain, every country's HYBRID chain starts with cache-side vendor

Reusable KYC: cross-account verification (in development)

New feature for reusing identity verification across multiple accounts within the same organization.

Added

  • Reusable KYC endpoints: /v1/individual/reusable_kyc
    • Share-token creation for reusable identity
    • Eligibility preview before reuse
    • Synchronous reuse operations
  • Integration guide: step-by-step Reusable KYC workflow documentation
  • Examples: request/response examples for all operations
  • Recipient-level handling: documented Document-only, Face-only, and combined reuse scenarios
  • Error catalog: eligibility error codes and remediation guidance
  • ReadMe navigation: featured in Individual API reference