This endpoint is used to update an existing ID verification request to one or more clients, and can be used to:

1. Associate new clients with an existing file (i.e. fileReferenceId).

2. Update client information that will be used in the ID verification process (e.g. update a client's email or phone number).

Note: if attempting to apply different settings to a client's verification request (e.g., banking login enabled/disabled, etc.), use the Re-Initiate Verification endpoint.

Note: if the client already has a pending ID verification request outstanding on this file or if the client has already completed the ID verification process and has a report available for review, updating their information will cancel the client's existing ID verification link and the client will receive a new link with the updated information.

Note: a new clientRequestId will be created and passed back for the updated verification request, and the previous clientRequestId will be marked as "Cancelled".

Tips on associating new clients with an existing file

If you are an integrator sending requests on behalf of multiple separate organizations (e.g., multiple law firms, brokerages, etc.) you will likely want to set the createNewClientRecord parameter to true for all requests so that a new client record is created in our system if a client already exists in varying statuses (pending, cancelled, review report, etc.) within the same or different files. This will ensure that the status of a client that already exists within or between separate organizations will not impact a subsequent request to the same client. A client exists if the email address has previously been used. This parameter can be used to support the following use cases:

• the same email address can be used multiple times within the same file (e.g., if two individuals wanted to use the same email address but needed to complete separate IDVs). Since multiple unique client records would be created, each IDV request can be sent with different settings, and each client can complete their own report using the same email address.


• the same email address can be used multiple times at the same time between different files (e.g., if Law Firm A and Law Firm B both requested independent reports for a client at the same time).

If the createNewClientRecord parameter is not used or set to false, the following logic would apply:

• if the client does not have a pending ID verification or an active existing ID verification report (i.e., this is a new client or the client's status is REQUEST NOT SENT or CANCELLED), then this endpoint will associate the client to the file and will automatically send a new request to the client.


• if the client already has a pending ID verification (i.e., the client's status is REQUEST PENDING), then this endpoint will associate the client to the file but will not send a new request to the client because an active request already exists. If the link needs to be resent to the client, use the Resend Link endpoint.


• if the client has an active existing ID verification report (i.e., the client's status is REVIEW REPORT, VERIFIED, or REJECTED), then this endpoint will associate the client to the file but will not send a new request to the client because an active report already exists for this client. To initiate a new ID verification request, use the Re-Initiate Verification endpoint.