Before using the API, the partner shall contact Klavi business representative and apply for security credentials. Security certificates include access key (i.e."AK") and secret key (i.e."SK").

Partner must keep safety certificates strictly to avoid leakage.

Suppose that the user's accessKey and secretkey are:

Learn how to securely obtain and manage security credentials for Klavi's API. This document explains the process of contacting Klavi's business representative and applying for access and secret keys. These keys serve to identify your API requester's ident

Signature algorithm

Apply security certificate

Splicing specification request string

Klavi ki

Klavi Ki docs

Overview

Platform overview

End-user journey

Product overview

How to get product

How to integrate

Usage console

Quickstart

Products

Connection update

Categorization API

Institution coverage

Return code

SDK & API integration

Version control

Develop guides

Category_checking (V1)

Category_creditcard (V1)

Income (V1.1)

Liabilities (V1.1)

Financial_insight (V1.1)

Risk_label_a (V1.1)

V1 - For Link clients

V2 - For OF clients

Change log

Risk_label_k360

Score_k1 (V1)

Score_l1 (V2)

Score_l2 (V2)

FGTS (V1)

INSS (V1)

Investment (V1)

Investment_transaction (V1)

Investment_advance (V1)

Investment_pdf (V1.1)

Investment_ipo (V1)

Corporate_checking (V1)

Gig_economy (V1)

Identity (V1)

Balance (V1)

Bank_loan (V1)

Identity data coverage

Categorias

Data time range coverage

Request structure

Public parameters

Spell the signature string

Calculate signature

Splicing authorization

Untitled

Return result and code

API invocation method

getInstitutionList

submitCredentials

checkStatus

submitMFAInfo

updateProducts

deleteAccount

Status Type

Callback

Institution credentials format

MFA format

Decryption of reports

Release History