Create an individual application

post

https://openapi.advance.ai/v1/individual/applications

Creates a verification application for the given externalUserId and levelId.
The system creates or links a profile and initializes application context from
profile data (plus optional fixedInfo, phone, email).

After returning, the system starts the verification workflow asynchronously.
The application status will transition through init -> pending -> completed
(or onHold if manual review is required). For AML-only levels the application
may reach completed within seconds. Use GET /v1/individual/applications/{applicationId}
to poll status, or subscribe to Webhook events (application.completed,
application.onHold, etc.) for real-time notifications.

Each profile may have at most one non-terminal application. The conflictStrategy
field controls behavior when an active application already exists:

RESUME_SAME_LEVEL (default): if the same levelId matches, return the existing application
REJECT_IF_ACTIVE: always return 409 conflict

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

externalUserId

string

required

User identifier in the caller system; used to create or link a profile.

levelId

string

required

Level ID. Must reference an active level.

fixedInfo

object

Input format for PersonInfo fields. Merge-patch semantics apply.

phone

string

ITU-T E.164 phone number; merged into application context.

string

RFC 5322 email; merged into application context.

conflictStrategy

string

enum

Defaults to RESUME_SAME_LEVEL

How to handle an existing non-terminal application for the same externalUserId:

RESUME_SAME_LEVEL: if an active application with the same levelId exists, return it directly instead of creating a new one; if levelId differs, return 409 conflict
REJECT_IF_ACTIVE: always fail with 409 when any non-terminal application exists

Allowed:

Headers

Idempotency-Key

string

length ≤ 64

Client-generated unique key to ensure idempotent POST requests. Valid for 24 hours.

X-Request-Id

string

Unique request identifier. Injected by the API gateway if not provided by the client.
The same value is available in the response body requestId field for business-layer tracing.

X-Trace-Id

string

Distributed tracing identifier. Injected by the API gateway if not provided by the client.
Used for cross-service request correlation in logs and monitoring.

Responses

201Application created successfully.

400Request validation failed. Possible causes: Missing required fields (externalUserId, levelId) Invalid field format (e.g. nationality not ISO 3166-1 alpha-3) levelId references a non-existent or inactive level

401Authentication failed. Access token is missing, invalid, or expired.

403Access denied. Possible error types: permission_error — account is not authorized for this service insufficient_balance_error — account balance is insufficient over_query_limit_error — query limit exceeded

429Rate limit exceeded.

500Unexpected server error.

503Service temporarily unavailable (e.g. distributed lock acquisition failed). Safe to retry.