Liveness Streaming Status [application/json]

POST

https://mostqiapi.com/liveness/streaming/async/status

Last modified:2025-05-15 13:13:14

This route allows you to check the status of the life proof process requested in the Liveness Streaming [application/json] route.

The status of a process can be checked for 1 hour after the initial request, ensuring enough time for monitoring and data retrieval.

The status can be:

Status	Description
TODO	The proof of life has not been started yet or is in progress.
DOING	The proof of life session has been started, meaning the user clicked "Start capture" and the process is ongoing.
DONE	The proof of life has been successfully completed. In this case, the result will contain values for the frontalImage and livenessScore attributes.
ERROR	An error occurred during the proof of life process.
EXPIRED	The proof of life session expired. This happens when the user does not complete the life proof within 3 minutes after clicking "Start capture."

Request

Header Params

Authorization

string

required

Authorization token obtained from the user/authenticate method.

Example:

Bearer {{bearer_token}}

Body Params application/json

processId

string

required

Process identifier code obtained through the /liveness/streaming/async/ route.

Examples

Example 1Example 2

{
    "processId": "{{processID}}"
}

Request samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

cURL

Example 1Example 2

curl --location --request POST 'https://mostqiapi.com/liveness/streaming/async/status' \
--header 'Authorization: Bearer ' \
--header 'Content-Type: application/json' \
--data-raw '{
    "processId": ""
}'

Responses

🟢200Ok

application/json

Body

result

object

required

List containing the result of the method.

processId

string

required

ID related to the asynchronous Liveness Streaming request process, called "processId". This ID will be used to check the status of the process and access the result of the liveness verification.

status

string

required

Proof of life status: TODO, DOING, DONE, ERROR, or EXPIRED.

livenessScore

integer

required

Confidence score (from 0 to 1) that indicates the likelihood of the user being real and present.

frontalImage

string <base64>

required

Binary file with the front image captured during the liveness verification. The image is encoded as a text string according to the RFC3548 standard using base64 encoding.

requestId

string

required

Unique identification code of the request to the server, which will be recorded in the service usage history.

elapsedMilliseconds

integer

required

Processing duration in milliseconds.

status

object

required

Object containing the status code and message of the response.

message

string | null

required

Internal status code. See the possible values in the mostQI error messages.

code

string

required

Status return message. See the possible values in the mostQI error messages.

errors

object | null

required

List of Error objects, the format is variable.

Examples

TODODOINGDONEEXPIRED

{
    "result": {
        "processId": "dbf9e398-98de-41d3-8b95-525026c00f96",
        "status": "TODO",
        "livenessScore": null,
        "frontalImage": null
    },
    "requestId": "aeYmNfTUBs2zhWOB4to55",
    "elapsedMilliseconds": 314,
    "status": {
        "message": "Ok",
        "code": "200",
        "errors": null
    }
}

🟠400Invalid authentication data

🟠400R101 A specified parameter is wrong

🟠400R125 Process expired or not found with the given ID

Liveness Streaming [application/json]

MultiAddress Parsing