latestOpenAPI 3.0.32026-07-2141248520.9 KB
880b27506cbb
IDV
At the end of the IDV data capture process with all photos and videos captured, signal to IDV provider that check is ready to analyse and check.
At the end of the IDV data capture process with all photos and videos captured, signal to IDV provider that check is ready to analyse and check. If this call is successful, an entity is populated with with any details supplied if it doesn't not already have a name.
post/v2/individuals/{entityId}/actions/idv/process
Headers
api_keystring required
Example:245c765b124a098d09ef8765....
Your API key provided by FrankieOne
X-Frankie-CustomerIDstring required
Example:12345678-1234-1234-1234-123456789012
Your Customer ID provided by FrankieOne
X-Frankie-CustomerChildIDstring
Example:87654321-4321-4321-4321-210987654321
Your Customer Child ID provided by FrankieOne
X-Frankie-Channelstring
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.
Request body
Example request
{
"providerReferenceId": "41cf9401f0f889616bef",
"token": "41cf9401f0f889616bef",
"comment": {
"commentId": "55fc5d54-46f7-49c8-bf78-e07ec79cd6e7",
"text": "Update after speaking to customer over the phone directly."
}
}Response
OK