KYC V2 APIIndividual Results

Update the status of Duplicate process results

Update the status of a set of Duplicate process results. The request body supports batch processing of duplicate results with the following components:

  • processResults: Array of UUID strings identifying specific duplicate Process Results to update - manualStatus: The resolution status for the duplicates, which can be one of:
    • FALSE_POSITIVE: When the flagged entities are determined to be different individuals (both records should be kept)
    • TRUE_POSITIVE_ACCEPT: Keep the current entity as primary and mark the result entity as duplicate (use when current record is more complete/accurate)
    • TRUE_POSITIVE_REJECT: Keep the result entity as primary and mark the current entity as duplicate (use when duplicate record is more complete/accurate)
  • comment: Optional documentation for the decision rationale, useful for audit trails and team communication

Path parameters

entityIdstringRequired

Unique FrankieOne identifier for an entity

Headers

api_keystringRequired
X-Frankie-CustomerIDstringRequired

Your Customer ID provided by FrankieOne

X-Frankie-CustomerChildIDstringOptional

Your Customer Child ID provided by FrankieOne

X-Frankie-ChannelstringOptional

Open string that can be used to define the “channel” the request comes in from. It can potentially be used in routing and risk calculations upon request. Default values that can be used are: api portal smartui Any alphanumeric string is supported though. Anything over 64 characters will be truncated.

X-Frankie-UsernamestringOptional

Username provided by API caller

Request

This endpoint expects an object.
processResultslist of stringsOptional

The process result IDs to update. These are the PROs created when a duplicate has been found.

manualStatusenumOptional

The status that the duplicate process result should be set to.

  • FALSE_POSITIVE: When the flagged entities are determined to be different individuals (both records should be kept)
  • TRUE_POSITIVE_ACCEPT: Mark the incoming entity as duplicate and keep the result entity as primary (use when current record is more complete/accurate)
  • TRUE_POSITIVE_REJECT: Keep the incoming entity as primary and mark the result entity as duplicate (use when duplicate record is more complete/accurate)
Allowed values:
commentobjectOptional

Response

OK

requestIdstringOptional

The unique request ID for the API call made.

processResultslist of objectsOptional

Errors