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 have access to fast, agile and secure financial services, the way they want. Learn more at https://qitech.com.br.
This documentation aims to describe the various endpoints of our APIs.
Note: In case of doubts at any stage of the process, please contact api@qitech.com.br detailing your problem/doubt and we will assist you.
First steps
Before starting operations by sending API requests to consume QI Tech services, it is important that an operator representing the originator company performs the following steps in sandbox environment.
Access Profile Creation
- Send an access creation request to the email api@qitech.com.br providing the following information:
- Company CNPJ
- Full name of the Master user
- CPF of the Master user
- Email of the Master user
- Cell phone number of the Master user
- After access creation 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 temporary password.
- When performing the first access to the platform, the Master user must reset the access password.
Starting the integration journey
There are several 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: Perform Token validation through the QI Tech portal Step 2: Perform key exchange and generate integration credentials Step 3: Perform authentication test Step 4: Configure webhook receiving URL
Real data from individuals and/or legal entities must not be used in QI Tech's Sandbox environments.
Important information
To use our API in production it is necessary to contact comercial@qitech.com.br for commercial contact and integration setup.
QI Tech webhooks should not be mapped in a restrictive manner. Additional fields may be included in webhook payloads returned by our APIs.
You can consult and resend webhooks following the detailed instructions in the documentation: Webhook Resending.