Trust

The video recognition interface is currently available in 19 languages, including:

• Chinese (Simplified)

• Dutch

• English (UK)

• English (US)

• Estonian

• Finnish

• French

• German

• Japanese

• Korean

• Italian

• Latvian

• Polish

• Portuguese

• Romanian

• Russian

• Slovak

• Spanish

• Swedish

At the end of each video identification (IDV) procedure, you can obtain the verification report in different formats:

• JSON format: for automatic integration into IT systems
  PDF format: for consultation and document archiving

Both formats are available through the dedicated API endpoint.

Additional options: you can also download individually:

• Document images (front or back)
• Facial recognition photo (selfie)

To initiate a video identification (IDV) procedure, the following mandatory data is required:

• Email: the email address of the user to be identified
• Full name: first name and last name of the user
• Redirect URL: the web page to which the user will be redirected at the end of the procedure

Important: the first name and last name must match exactly those shown on the identity document that will be presented during verification. Any discrepancies may result in a negative outcome of the identification procedure.

In order to make a POST/email-start request, it is necessary to pass the parameter “Email address”.

The response provides the following information about the searched email

• id, needed later to check the status of the request
• status of the email (valid, invalid, risky, unknown)
• validity and details of SPF and DMARC configurations
• indication if the email is from a free provider (e.g. Gmail, Outlook). Gmail, Outlook)
• recognition of temporary, disposable e-mails
• presence of catch-all domain (accepts all e-mails)
• verification of active anti-spam systems on the mail server
• availability of the mailbox (whether full or not)
• correction suggestions in case of errors in the domain of the e-mail
• indication whether the e-mail address is a role-based account (e.g. admin@, support@, info@)
• verification of IP addresses
• request date and time
• update date
• request status ( NEW, WAIT, DONE)

Average response times are a few seconds.

When making a request, it is also possible to set up a callback so that you are notified when the response is available.

In case it is not possible to handle the request within the first 10 seconds, a partial response will be returned, with status “NEW”, and its id to handle the request asynchronously via the GET/email-start method.

To make a request to POST /mobile-start, you need to pass the parameter 'Mobile phone number', including the international dialing code.

The response provides the following information about the queried phone number:

• Mobile number validity
• Country code
• Country
• Number validity relative to the country
• Type of number (in this case, always mobile)
• Entered number
• Formatted number
• Request date and time
• Update date
• Request status (NEW, WAIT, DONE)
• Original operator
• Current operator
• Roaming
• Ported (change of operator with the same number)
• Mobile number country prefix
• Details
• Request ID

The average response time is a few seconds.

You can also set a callback during the request phase to receive a notification when the response is available.

If the request cannot be processed within the first 10 seconds, a partial response with status 'NEW' will be returned, along with an ID to manage the request asynchronously using the GET/mobile-start method.

Yes, during the POST requests, you can also set a callback to receive a notification when the response is available.

IMPORTANT: When configuring the callback, you must enter a valid URL that can handle POST requests. You can also populate the “custom” field with any additional data you wish to include in the callback response.

To make a request to GET, you need the ID parameter, obtained using the POST method.

The response provides details of a previous search, allowing you to check its status and verify the available information.

The service are available globally.

In response to a POST request for mobile, phone, email, IP, and URL services, three states may be returned:

• NEW: the request has just been received and is waiting to be processed.

• WAIT: an intermediate state indicating that the request is still being processed.

• DONE: the request has been completed; in this case, the full response with all data will be available.

For mobile, phone, URL, IP, and email services, the response is generally returned within a few seconds. If it is not possible to complete the request within the first 10 seconds, a partial response with status ‘NEW’ and the corresponding ID will be provided, allowing the request to be handled asynchronously via the GET method.

For IDV services, the response is normally provided within a few seconds, or within 2 minutes in cases where human intervention is required.

Costs vary depending on the type of service:

For the endpoint POST /mobile-start/{mobile-phone} the cost starts from €0.010 with a subscription or €0.039 with pay-as-you-go billing.

For the endpoint POST /mobile-advanced/{mobile-phone} the cost starts from €0.019 with a subscription or €0.049 with pay-as-you-go billing.

For the endpoint POST /email-start/{email} the cost starts from €0.0008 with a subscription or €0.03 with pay-as-you-go billing.

For the endpoint POST /email-advanced/{email} the cost starts from €0.019 with a subscription or €0.049 with pay-as-you-go billing.

For the endpoint POST /ip-advanced/{ip} the cost starts from €0.019 with a subscription or €0.049 with pay-as-you-go billing.

For the endpoint POST /url-advanced/{url} the cost starts from €0.019 with a subscription or €0.049 with pay-as-you-go billing.

For the endpoint POST /idv-flash-start the cost starts from €0.65 with a subscription or €0.85 with pay-as-you-go billing.

For the endpoint POST /idv-flash-advanced the cost starts from €0.89 with a subscription or €1.25 with pay-as-you-go billing.

For the endpoint POST /idv-expert the cost starts from €1.690 with a subscription or €2.90 with pay-as-you-go billing.

For the endpoint POST /idv-certified the cost starts from €2.90 with a subscription or €4.50 with pay-as-you-go billing.

For the endpoints GET/mobile-start and GET/email-start a fair use policy applies, under which they are free up to 1,440 calls per day; beyond this limit, a charge of €0.001 per request applies.

Yes, currently an annual subscription for the HLR service can be activated, allowing you to save on the cost of each call. In the API-specific Subscriptions section, you can view the available options (with prices and savings percentages) and activate the subscription you prefer.

In the Usage section, at the API level, you can monitor both free and paid requests made through a subscription or top-up. The data is available in graphical format (monthly and yearly) and as a textual summary.

There are no limits for IDV services: you can make as many requests as you want without restrictions.
For mobile, phone, email, IP, and URL services, the API can handle up to 50 requests per minute. If this limit is exceeded, a partial response with status “NEW” and a unique ID will be returned, allowing you to complete the request asynchronously using the GET method.