Skip to main content

Introduction

We are the first financial institution to create an exclusive Bank-as-a-Service (BaaS) model in Brazil. Our goal is to help any Fintech/Credit Manager or company to access fast, agile, and secure financial services, in any way they want. Learn more at https://qitech.com.br.

This documentation aims to describe the various endpoints of our APIs.

Note: If you have any questions at any stage of the process, please contact us at api@qitech.com.br detailing your problem/question and we will assist you.

Getting Started

Before beginning operations by sending API requests to consume QI Tech services, it is important that a representative operator of the originating company completes the following steps in the sandbox environment.

Creating an Access Profile

  1. Send a request for access creation to the email api@qitech.com.br containing the following information:

    1. Company CNPJ
    2. Full name of the Master user
    3. CPF of the Master user
    4. Email of the Master user
    5. Mobile phone number of the Master user
  2. After the access is created by the QI Tech team, the Master user will receive an email with a link to access the QI Tech platform in sandbox and a provisional password.

  3. When accessing the platform for the first time, the Master user must change the access password.

Starting the Integration Journey

There are various combinations of endpoints that can be used according to the partner's needs, but the first three steps are universal regardless of the services used:

Step 1: Validate the Token through the QI Tech portal;
Step 2: : Exchange keys and generate integration credentials;
Step 3: Perform the authentication test;
Step 4: Configure the webhook receiving URL;

Important Information

To use our API in production, it is necessary to contact commercial@qitech.com.br for commercial engagement and integration configuration.

Attention!

QI Tech webhooks should not be mapped in a restricted way. Additional fields can be included in the payloads of the webhooks returned in our APIs.