INinfobip
connectivity
biometrics
kyc-session

Receive KYC Session Results

Webhook which will be called with information about the KYC session status and results. The webhook URL provided in the Create KYC Session request will be called with the POST method that contains all the info in JSON format. It only expects 200 OK status with no content in response.

postWebhookreceive-kyc-session-results

Payload

sessionIdstring required

Unique session identifier.

partnerReferencestring required

Your identifier of the end user performing a scenario sent in the initial request.

status'CREATED' | 'ACTIVE' | 'SUCCESS' | 'EXPIRED' | 'CANCELED'

Current session status.

Example payload

{
  "sessionId": "efc373be-ab6d-4c63-b798-1f65b7b4b2b3",
  "partnerReference": "MyRef-jqhof",
  "status": "SUCCESS",
  "data": {
    "mrzData": {
      "name": "NAME",
      "surname": "SURNAME",
      "documentNumber": "123456789",
      "birthDate": "000101",
      "expiryDate": "250101",
      "country": "HRV",
      "sex": "F",
      "nationality": "HRV",
      "optionalData": [
        "mrzOptionalItem1",
        "mrzOptionalItem2"
      ],
      "personalNumber": "01234567890",
      "type": "P"
    },
    "faceMatch": true,
    "faceDistance": 0.232,
    "faceConfidenceScore": 83,
    "biometricReference": "usr_eb1cfc67ead74fc29ff2c65c4cec2baf",
    "biometricVector": [
      -0.09652680158615112,
      0.07107646763324738,
      -0.029479391872882843,
      -0.006973235867917538
    ]
  }
}

Response

Your server returns this code if it accepts the callback

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.