List identity verification KYC artifacts

GET

https://tenant.api.corpx.com/v1/identity-verifications/:verificationId/artifacts

GET

/v1/identity-verifications/:verificationId/artifacts

curl https://tenant.api.corpx.com/v1/identity-verifications/verificationId/artifacts \
     -H "X-Tenant-Id: X-Tenant-Id" \
     -H "Authorization: Bearer <token>"

{
  "verificationId": "idv_01J8Y7C8D9E0F1G2H3J4",
  "count": 2,
  "items": [
    {
      "artifactId": "art_01J8Y9A0B1C2D3E4F5G6",
      "kind": "unico_evidence_set",
      "document": "12345678909",
      "fileName": "unico_evidence_set.jwt",
      "contentType": "application/jwt",
      "sha256": "3f9a2b1c0d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a",
      "createdAt": "2026-09-24T14:08:12Z",
      "sizeBytes": 14203,
      "downloadUrl": "https://downloads.corpx.com/identity-verifications/art_01J8Y9A0B1C2D3E4F5G6"
    }
  ]
}

The caller must also be the master M2M credential, send X-Tenant-Id, and have the identity verification’s tenant context.

Returns the KYC evidence files produced for this tenant-scoped verification. Because these files contain sensitive biometric and identity material, this route requires the dedicated `kyc.read` scope and the tenant's `kyc_artifacts` feature. The caller must also be the master M2M credential, send `X-Tenant-Id`, and have the identity verification's tenant context.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

verificationIdstringRequired

Standalone identity verification identifier returned by the creation endpoint.

Response

KYC artifacts for the verification.

verificationIdstring

Standalone verification identifier.

countinteger

Number of returned artifacts.

itemslist of objects

Evidence files produced by the provider.

Errors

401

Unauthorized Error

403

Forbidden Error

404

Not Found Error

500

Internal Server Error

Authentication

Path parameters

Headers

Response

Errors