KYB Application

✅

KYB Application — Enterprise Lifecycle Management

Submit enterprise information for review through forms or OpenAPI mode, with a focus on customers who need platform assistance for KYB review.

Company Profile→

AdvanGuard creates or updates a Company Profile with verified data when it processes a submitted KYB Application.

Company Application→

The Company Application is a verification session for a legal entity (KYB). It links a Company Profile to a Level, runs business registry checks, beneficial owner verification, and AML screening, producing a final result.

Application Lifecycle

Once the application is submitted, AdvanGuard KYB will automatically trigger all risk checks. After passing, it will enter the manual review queue if necessary, and the auditor will make the final judgment based on the risk control results.

Final status	Meaning	Customer action
`APPROVED`	Application has been approved	None — proceed with onboarding
`REJECTED`	Application has been rejected	Notify applicant
`PENDING_RESUBMISSION`	Application requires resubmission with corrections	Revise materials and resubmit
`PENDING_REVIEW`	Awaiting manual review by compliance team	Wait for decision, or check status via API

Submission Modes

Depending on whether there is a need for questionnaire functionality or custom questionnaire templates, the corresponding configuration and submission mode differ:

Mode	Questionnaire	Description
Mode 1 API Call Submission	Required & configured	Customer calls Submit Application via Form API using flat key-value structure. The server retrieves questionnaire structure based on `qnreIdentifierVersion` and performs type conversion automatically.
Mode 2 Form Mode	Required & configured	Customer configures questionnaire template on the AdvanGuard platform, then embeds the generated form link into their website or app. End users complete and submit the form; the AdvanGuard server automatically calls the Submit Application API internally — no additional API call required by the customer.
Mode 3 Payload Mode	Not required	Customer sends complete nested JSON objects via Submit Application via Payload. Suitable for server-to-server integrations that do not need questionnaire functionality.

Integration Steps

Acquire Account & Access Token

Contact advance.ai to obtain official or test account credentials. Use the Token Authentication API to exchange for a Bearer Token. All subsequent requests must carry this token in the Authorization: Bearer {token} header.

💡 Test account and official account share the same domain openapi.advance.ai; the environment is distinguished by account credentials.

Optional: Configure Questionnaire

If you choose Mode 1 or Mode 2, configure a questionnaire template on the AdvanGuard platform in advance and click Publish after configuration is completed. Note the qnreIdentifierVersion value — you will need it for Mode 1 API calls.

Select Submit Mode & Integrate

Choose one of the following three modes based on technical capabilities and business scenarios:

Mode 1: Client Server directly calls Submit Application via Form with a flat key-value list. Confirm the qnreIdentifierVersion via Preview Questionnaire API or in the Application list of the AdvanGuard platform before submission. Optionally register a Webhook to receive real-time application status change notifications.
Mode 2: After questionnaire configuration, embed the generated form link into your website or app. End users complete and submit; AdvanGuard handles the rest.
Mode 3: Call Submit Application via Payload to send complete nested JSON to the AAI server. Suitable for customers who do not need questionnaire functionality.

⚠️ The applicationId is returned in the response. Persist and store it — all subsequent queries and operations depend on this ID.

Optional: Upload & Attach Supporting Documents

To attach supporting documents, such as business license or equity stake structure diagram, to the application:

Call Upload Document to upload the file and obtain a documentId.
Call Add Application Document to associate the document with the application and the specific declared entity, such as company or individual.

Query Application Status & Risk Verification Results

Mode 1 (Platform): Log in to the AdvanGuard platform to directly view the application status and verification results without calling the API.
Mode 2/3 (API): Use Get Application Risk Checks to check the status of each risk verification; use Get Application Detail to obtain complete application details.

💡 Register a Webhook to receive state change notifications to reduce the number of active polling calls.

Process Final Results

The final status of the application is APPROVED or REJECTED. If the status is PENDING_RESUBMISSION, the customer needs to revise the materials and resubmit the application.

API List

#	Module	API	Description
1	Token Auth	Token Authentication API	Obtain the Access Token required for all subsequent APIs. The Token has a validity period and needs to be refreshed regularly.
2	Application Management	Submit Application via Form	Submit using flat key-value structure. Server retrieves questionnaire schema based on `qnreIdentifierVersion`. Suitable for front-end docking or simple scenarios.
3		Submit Application via Payload	Submit with complete nested JSON. Suitable for server-to-server integration without questionnaire requirement.
4		List Applications	Retrieve paginated application list. Supports filtering by status, date range, and application IDs.
5	Application Query	Get Application Detail	Retrieve complete application info including subject company, related companies, and individuals with merged and original data.
6		Get Application Risk Checks	Retrieve all risk check statuses, including AML, IDV, registry, BO, and card network, for an application.
7	Document Management	Upload Document	Upload supporting files, such as PDF or images, and obtain a `documentId` for association.
8		Add Application Document	Associate an uploaded document with a specific declared entity in an application.
9		Download Document	Retrieve the download URL and metadata for an uploaded document. Download URLs are temporary pre-signed links.