In addition to synchronous call - where the customer initiate a call and is immediately redirected to the network and media test, then to the first available operator - LiveID+ also supports asynchronous calls.
In this mode, the customer submits their information to request a video identification, which an operator will handle at a later time (e.g.: through scheduled appointment).
This can be done using two methods: pushAsyncCall and service-asyncall.
pushAsyncCall method puts a video identification call in the system without it being immediately redirected to platform test and then to the first available operator.
Calls entered using pushAsyncCall are linked to the unique ID provided in the response and can then be initiated using service-asyncall.
UTF-8 Base64 encoded JSON object containing all the configuration parameters for starting a call.
The object to encode must be structured as follows:
{
id_organization: ...
id_process: ...
json: ...
}See service-webrtc-test or service-start (depending on the method passed) for parameters details.
Given that all data is already encoded, base64 encoding of the json parameter is not required in case of method=start.
The method used to start the call ("start" is preferred).
"live": the call is started using service-webrtc-test"start": the call is started using service-start
- Testhttps://liveid.test.namirialtsp.com/api/service/pushAsyncCall
- Productionhttps://liveid.namirialtsp.com/api/service/pushAsyncCall
curl -i -X POST \
https://liveid.test.namirialtsp.com/api/service/pushAsyncCall \
-H 'Content-Type: application/json' \
-d '{
"b64Data": "string",
"method": "live",
"expire": "2019-08-24"
}'{ "service": "string", "success": true, "uId": "string" }