API spoof detection

The spoof detection based on liveness check provides possibility to check if the person is not alive and a printed image, mask or display is used. The two main detections are available: distant and nearby. Mostly, the distant is optimized for seamless access and analysis of approaching persons. Nearby detection type is optimized for persons who are standing close to the camera in order to be identified. It is possible to use both these detections simultaneously, but it is not allowed to use same type of detection with both cpu and gpu.

The spoof detection based on liveness check can be performed using a single face on given image via API endpoint POST /api/v1/Faces/SpoofCheck in the entity Faces. As mentioned above

type of spoof detector in attribute "spoofDetectorResourceIds"
Supported values are: liveness_distant_any_remote, liveness_distant_cpu_remote, liveness_distant_gpu_remote, liveness_nearby_any_remote,liveness_nearby_cpu_remote, liveness_nearby_gpu_remote
For Cloumatcher purposes this detector supports only these values: liveness_distant_any_remote, liveness_distant_cpu_remote, liveness_nearby_any_remote,liveness_nearby_cpu_remote
spoof detection parameters in "spoofCheckConfig"

{
  "image": {
    "data": ""
  },
  "faceDetectorConfig": {
    "minFaceSize": 35,
    "maxFaceSize": 600,
    "confidenceThreshold": 450
  },
 "faceDetectorResourceId": "cpu",
  "spoofDetectorResourceIds": [
    "liveness_distant_cpu_remote"
  ],
  "spoofCheckConfig": {
    "distantLivenessScoreThreshold": 90,
    "nearbyLivenessScoreThreshold": 90,
    "distantLivenessConditions": "default",
    "nearbyLivenessConditions": "default"
  }
}

The spoof detection based on the liveness check, as described above, was also integrated into the entity Watchlists. In this way, the user is enabled to perform the liveness check in a single API endpoint call at face matching against specified watchlists. You can configure the liveness check via following part of the API endpoint POST /api/v1/Watchlists/Search/ . This endpoint is designed for to search specified watchlists for matches with given image.

In this case supported values for "spoofDetectorResourceIds" are: none,liveness_distant_any_remote, liveness_distant_cpu_remote, liveness_distant_gpu_remote, liveness_nearby_any_remote,liveness_nearby_cpu_remote, liveness_nearby_gpu_remote

For Cloumatcher purposes this detector supports only these values: liveness_distant_any_remote, liveness_distant_cpu_remote, liveness_nearby_any_remote,liveness_nearby_cpu_remote

...
  "spoofDetectorResourceIds": [
    "none"
  ],
  "spoofCheckConfig": {
    "distantLivenessScoreThreshold": 90,
    "nearbyLivenessScoreThreshold": 90,
    "distantLivenessConditions": "default",
    "nearbyLivenessConditions": "default"
  }
}
...