Skip to main content

Introduction

Welcome to QI Tech's Account Event API! This API provides access to monitoring services and event rules within your platform's accounts.

While this API can be used for device validation alongside the Device Scan and Device Registration APIs, it is also versatile enough for other validations such as:

  • Logins.
  • Screen access.
  • Password changes.
  • Registration data updates.
  • Pre-transaction validations.
  • Liveness Validation.

You can use our API to access endpoints for evaluating the following event types:

  • Device Validation - Used for validating a device's unique identification.
  • Pre Pix Transaction - Used for the pre-validation of Pix transactions.
  • Registration Data Validation - Used for validating registration data.

Different event types can be implemented depending on your system's specific needs.

On the side, you can view the API implementation using curl. These examples serve as a guide for you to adapt the code to your preferred programming language.

Having trouble?

Having Trouble? We aren't a company that hides behind an API! Get in touch with our support team and we will respond as quickly as possible. Feel free to call us if you need an immediate answer!

We Love Feedback

Even if you have already solved your problem or if it was something simple (like a typo or a minor organizational issue), please send us an email. This helps us make our documentation more practical so the next person doesn't have to face the same hurdles you did!

Environments

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

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

Real personal or corporate data must not be used in QI Tech's Sandbox environments.

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

HTTPS Only

For security reasons, all communication with QI Tech APIs must be performed via HTTPS. To prevent accidental HTTP calls, our server only makes port 443 available with TLS 1.2 communication. Calls made using other protocols will be automatically denied.