For a deeper look into our World Check One API, look into:

Overview |  Quickstart |  Documentation |  Downloads

question

Upvotes
Accepted
3 0 0 3

Questions Regarding World Check One

Hello,

I have a few questions about the World Check One service.

  1. Is there a way to configure the name match threshold via the API, per screening request?
  2. Do secondary fields (ie. DOB and location) have any effect on the match-strength of a result or on which entities are matched in a search?
  3. We need to obtain information about associates, AKAs, all PEP roles and whether the match is deceased, for each match identified in a search - do you offer any way to do this other than to send requests to the below endpoints for each match?
/reference/records/{id}
/reference/records/{id}/pep

4. In the same way as the above, we need to capture adverse media information for each match in a search - does the MediaCheck service provide the ability to retrieve adverse media articles for a specific match?

world-check-oneapi
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
Accepted
1.4k 5 2 2

Hi @mark06

1. Yes, we do have a way so that you can configure the "Name Match Threshold"
Login to WC1 UI => Groups => WORLD-CHECK SETTINGS => Configure Name Matching Threshold.
1658321513583.png
2. Secondary fields doesn't have any impact on the "matchStrength" of the results, however, it will give you the granular view as whether the secondary fields which you had added as part of request are matching with the WC records or not (If YES, then fieldResult will be "Matched" otherwise it will show as "UNKNOWN" "NOT MATCHED")



1658321978230.png
3. Unfortunately, there is no other way to get the WC records (via the API) except below API endpoints.

  1. /reference/records/{id}
  2. /reference/records/{id}/pep

4. You can utilize the "SEQ-case-mediacheck-article-content: Work with single MediaCheck article content" API endpoint to get the desired details.


Please feel free to reach out to us if you have any additional questions.


Thanks

Vivek Kumar Singh


1658321513583.png (45.9 KiB)
1658321978230.png (15.1 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1.4k 5 2 2

Hi @mark06

Thanks for your query!

Please allow us to review the details, will get back to you shortly.


Thanks
Vivek Kumar Singh

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
3 0 0 3

Hi Vivek,
Thanks for your reply. Considering the information that we require and your answer to #3, could you confirm that you support the following sequence - particularly with regard to the number and frequency of requests:


First:
/cases/screeningRequest

then, immediately after, for each matched entity:
/reference/records/{id}
and
/reference/records/{id}/pep


Thanks

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Hi @mark06


Thanks for your query.


Endpoint sequence depends on the use case, however, your sequence of API calls are optimal.


Thanks

Vivek Kumar Singh