## October 16, 2026 — developer portal

This documentation edition organizes the KYC B2B contract into guides, reference, downloads and local simulation. The source specification declares `info.version=1.0.0`. That version identifies the documented contract; publishing guides does not announce a behavioral API change.

The public reference documents four supported Tenant operations and two legacy evidence routes that return `403 evidence_access_restricted`, reserved for internal Admin. Postman includes only the four supported operations. We do not publish Admin operations, internal sessions or infrastructure controls. The exporter combines the curated source with the restriction verified in current code, without importing the application.

## How to assess an update

Before updating your consumer, compare required fields, enums, error responses and authorization. Preserve handling for documented values, and do not confuse an article’s revision date with an operational environment’s version.

Repeat idempotent creation, reads, results and webhook tests. Verify the bytes used for HMAC and event deduplication. If your application downloads files, confirm scopes, IPs and file types too.

## Keep an integration record

Record the specification version used and when your client was reviewed. An editorial guide change does not automatically require migration. Incompatible changes need specific contract-evolution guidance.

Download the [OpenAPI specification](/downloads/kyc/openapi.json), explore [examples](/en/developers/kyc/examples-and-downloads) and use the [reference](/en/developers/kyc/reference) to confirm documented behavior before modifying code.