Schemas

Name of the service

Current status of the service

Expected availability date

Detailed description of what the service does

Key features that will be available

Contact email for more information or early access

URL to sign up for launch notifications

Link to documentation about the upcoming service

Unique session identifier for this liveness verification

Status of the liveness verification

Confidence score of liveness detection (0-100, where 100 is highest confidence)

Boolean indicating if the person is determined to be live (not a spoof)

Base64-encoded reference image captured during liveness check

Array of base64-encoded audit images captured during the liveness check process

ISO-8601 timestamp when the session was created

Human-readable message about the verification result

Result of AWS Rekognition face liveness verification with confidence score and audit images

Result of AWS Rekognition face comparison between two images with similarity score and quality metrics

Similarity score between the two faces (0-100, where 100 is identical)

Boolean indicating if the faces match based on the threshold

Confidence score for the face comparison (typically same as similarity)

Threshold used to determine if faces match (default: 80.0)

Quality metrics for the source image (first image compared)

Quality metrics for the target image (second image compared)

Human-readable message about the face match result

Brightness level of the image (0-100)

Sharpness level of the image (0-100)

Optional client-provided session identifier for tracking

Optional settings for the liveness session

S3 output configuration for storing audit images

Maximum number of audit images to capture (0-4)

Unique session identifier to use for liveness verification

Current status of the liveness session

ISO-8601 timestamp when the session was created

ISO-8601 timestamp when the session will expire (typically 15 minutes after creation)

Indicates if this document result was created by merging multiple files (e.g., front and back of ID card)

List of original filenames that were merged to create this document result

Explanation of why files were merged (e.g., 'Front and back sides of the same identity document')

Original filename of the uploaded document

High-level category classification of the document

Specific document type identification

AI confidence score for the classification and extraction (0.0 to 1.0, where 1.0 is highest confidence)

Extracted data fields from the document. Structure varies by document type:

Identity Documents:

• id_number, full_name, date_of_birth, gender, place_of_birth, expiry_date, nationality, etc.

Address Documents:

• account_number, full_name, address, street, city, postal_code, billing_date, provider, etc.

Income Documents:

• employee_name, employer, employee_id, gross_pay, net_pay, tax_deducted, pay_period, etc.

Entity Documents:

• company_name, registration_number, registration_date, company_type, directors, address, etc.

Compliance Documents:

• tin_number, company_name, issue_date, expiry_date, tax_status, etc.

Time taken to process this specific document in milliseconds

Optional metadata about document processing, such as merge information when multiple files were combined

Processing mode used: SINGLE_PASS for single files, BATCH for multiple files

AI provider and model used for verification

Total number of AI tokens consumed (if available)

Number of cached tokens used for optimization (if available)

Total number of logical documents identified (may differ from files due to merging)

Total number of physical files uploaded

List of unique document categories found

List of specific document types identified

Average confidence score across all documents (0.0 to 1.0)

Total processing time for all documents in milliseconds

Breakdown of documents by category

Unique identifier for this verification request

ISO-8601 formatted timestamp when the verification was processed

The type of verification that was performed

Overall status of the verification request

Array of individual document verification results

Aggregate statistics across all processed documents

Technical metadata about how the verification was processed

URI reference that identifies the problem type

Short, human-readable summary of the problem type

HTTP status code

Human-readable explanation specific to this occurrence of the problem

URI reference that identifies the specific occurrence of the problem

ISO-8601 timestamp when the error occurred

Unique request identifier for tracking and debugging

Array of field-level validation errors (if applicable)

Name of the field that failed validation

Validation error message

The rejected value (if applicable)