Skip to main content

Introduction

Welcome to the QI Tech Authentication Session Management API! This API was designed to control the complete user KYC flow!

This service organizes the authentication process, enabling the creation of KYC registration sessions with customized flows and use of other QI Tech authentication services:

  • Device Scan
  • Face Recognition
  • OCR

This way, it is possible to start the registration information collection flow through the link returned by the API. Once started, the web page will be responsible for guiding the user through the KYC steps defined in that session.

Furthermore, by being directly integrated with the other services described above, it is able to collect the information necessary to complete the authentication flow. With this information, it will be possible to perform the desired analysis on other QI Tech services, such as individual registration or a pre-transactional analysis, for example.

Problems?​

We are not a company that hides behind an API! Contact our support and we will respond as quickly as possible. Feel free to call us if you want a quick response!

We Love Feedback​

Even if you have already resolved your issue or if it is very simple (even a typo or inadequate organization that you have noticed), send us an email so we can make the documentation increasingly more practical and the next person won't have to suffer the same pains you did!

Environments​

We have two environments for our clients. The base URLs for the APIs are:

  • Production - https://api.caas.qitech.app/auth_session_manager/
  • Sandbox - https://api.sandbox.caas.qitech.app/auth_session_manager/
Important Notice!

Real data from individuals and/or legal entities must not be used in QI Tech's Sandbox environments.

In the Sandbox environment, submitted analyses are not charged and are responded to according to the rule configured for the event.

HTTPS Only​

For security reasons, all communication with QI Tech APIs must be carried out using HTTPS. To ensure that, due to inattention or any other reason, no HTTP calls occur, this server only makes port 443 available with TLS 1.2 communication. Calls made using other protocols will be automatically denied.