Skip to main content

Process Unified Api session data

POST 
/unified/process

This endpoint allows you to execute multiple KYC services in a single request by aggregating them into a unified flow.

Request Payload Behavior​

The request body must contain the combined (intersection) of all required properties for each service you include in requestedServices.

How it works:​

  • Each service may require:
    • Start Session parameters
    • Process parameters
  • If a service supports both start session and process, you must provide all required fields for both steps.
  • If a service only supports process, then you only need to provide the fields required for that step.

Example​

If you request:

{
  "requestedServices": ["FaceMatch", "DataMatch"]
}

Then your payload must include:

  • All required fields for:
    • FaceMatch → Start Session
    • FaceMatch → Process
    • DataMatch → Process (if it does not have start session)

Important Notes​

  • Missing required fields for any requested service will result in validation errors.
  • You should consult the documentation of each individual service to determine:
    • Which fields are required for start session
    • Which fields are required for process

Summary​

  • Think of this endpoint as a merged schema of multiple services
  • The payload must satisfy all required inputs across all selected services

Request​

Responses​