Biolink

The Biolink module performs asynchronous analysis of the received data for more comprehensive validation.

How the Biolink Module Works

The Biolink module performs its analysis asynchronously, processing data in the background without impacting the main application flow. During this process, various relevant pieces of information are cross-referenced, including identity validation of the customer who made the purchase.

⚠️

For triggering the Biolink message, the fields Name and Transaction Value are mandatory.

The analysis response can be checked later, allowing the system to make decisions based on the results as soon as they are available.


Response POST

Represents the integration execution response. If you have contracted more than one module, you may receive all at once. Modules not contracted will not be returned.


Result

FieldDescriptionTypeRequired
executionIdExecution IDGuidYes
analysisIdAnalysis IDGuidYes
transactionIdTransaction IDStringYes
biolinkBiolink resultBiolink ResultNo

Biolink Result

Represents the result of a biometric analysis.

FieldDescriptionTypeRequired
statusAnalysis statusStringYes
scoreBiometric analysis scoreDoubleNo

JSON

{
  "executionId": "string",
  "analysisId": "string",
  "transactionId": "string",
  "biolink": {
    "status": "string",
    "score": 0,
}

Response GET

Represents the execution response of the analysis query.


Result

FieldDescriptionTypeRequired
analysisIdAnalysis IDGuidYes
transactionIdTransaction IDStringYes
biolinkBiolink resultBiolink ResultNo

Biolink Result

Represents the result of a biometric analysis.

FieldDescriptionTypeRequired
statusAnalysis statusStringYes
identifierIdIdentification IDStringSim
scoreBiometric analysis scoreDoubleNo

JSON

{
  "analysisId": "string",
  "transactionId": "string",
  "biolink": {
    "status": "string",
    "identifierId": "string",
    "score": 0
  }
}

Response Error

Represents the details of a problem returned by the API in case of error.

FieldDescriptionTypeRequired
typeURI identifying the specific problem type. Can be used to categorize the error.StringNo
titleDescriptive title of the problemStringYes
statusHTTP status code associated with the problemIntegerYes
errorsValidation errorsObjectYes
instanceURI identifying the specific instance of the problemStringNo

JSON

{
  "errors": {
    "string": [
      "string"
    ]
  },
  "type": "string",
  "title": "string",
  "status": 0,
  "traceId": "string"
}