Person Management
Last updated
Last updated
Following the collection(s) creation, let's start enrolling some person(s) in the collection.
PUT
/person
This endpoint is to enroll or update a single person. For bulk person enrollment, please refer to PUT/persons
Headers
Body
person_id
Required: Yes
Type: string
Example:
Person id must be unique and defined, using same face with different person id will result duplicated record, be aware the person_id is case-sensitive.
person_name
Required: Yes
Type: string
Example:
Person name must be defined during enrollment. You can also update an enrolled person's name in later stage, as long the person_id remains the same
check_duplicates
Required: Yes
Type: boolean
Default value: false
Accepted values: false, true
Based on the set similarity score, this feature checks if there is a duplicated enrollment in a collection. If value set as true, enrolling a duplicate person is not allowed.
check_liveness
Required: Yes
Type: boolean
Default value: false
Accepted values: false, true
collection_name
Required: Yes
Type: string
Example:
Please create a collection first before enrolling person(s). Else an error "The requested entity could not be found." will return
duplicate_check_min_similarity
Required: Yes
Type: float
Default value: 0.7
Example:
It's recommended to keep the default value to check the duplicate enrollment. If "check_duplicates" set as false, "duplicate_check_min_similarity" will not be used
face_base_64
Required: Yes
Type: string
Example:
Use base64 encoded string to enroll the face, one image should have only one face
face_storage_type
Required: Yes
Type: string
Accepted values: "NoStorage", "StoreThumbnails", "StoreFullImage"
Example:
"NoStorage" = do not store any face image "StoreThumbnails" = store only thumbnails (cropped face from the given image) "StoreFullImage" = store full base64 image
metadata
Required: Optional
Type: dict
Example:
Metadata is a customizable field that allows to put additional info while enrolling a person. You can add N number customized fields for your use case.
Response
If set to true, the liveness check is conducted during the person enrollment. If the person is successfully enrolled, means the face is live, else an error of "ERR_LIVENESS_ERROR" will return if face is not live, and person is not enrolled. Check
Content-Type
application/json
x-api-key
<your-api-key>