KYC6 Search API 3.0 details


The Search API enables individuals and companies to be queried against our proprietary AML database. All information available through the KYC6 application is accessible, e.g. relationships, article summaries, and corresponding URLs.

The API provides access to the following datasets: PEPs, Sanctions, Regulatory Enforcement Lists, Profiles of Interest, Insolvency, Disqualified Director, Regulatory Enforcement List.

Archive size
Over 4m Individuals and Businesses
Archive history
Since 2015
Information source
Content type
Individuals and Businesses
Delivery protocol
Authentication type
API Key Header
Response format
Update frequency
Point in time

Frequently asked questions

If I search "Donald Trump" and then search again a day later, is that two separate searches?

Yes, each search is considered unique as we don’t pass a “Search Id” as part of the request or response.

How do I get rid of false positives and automate the responses for on-boarding?

The nature of the data means that it’s impossible to eliminate false positives entirely as there is no specific unique identifier such as a passport number or national ID, but we can make suggestions to reduce false positives as much as possible. However this will need to be tested in-line with your risk-based approach. The best practice matching criteria for reducing false-positives is “Forename + Surname + DOB/YOB + Country” as this provides multiple data points to match on.

For on-boarding many clients just search against PEP & Sanctions rather than all data sets, and in particular adverse media as it is a much larger datasets which can introduce false positives. By nature, adverse media profiles aren’t always as complete as PEP or Sanction profiles because the evidence isn’t readily available. In the request, a “Threshold” can be set to filter out matches below a given score, the default we suggest is 70 however this could be increased using the matching criteria mentioned above. Again, this will need to be tested in-line with each client’s risk-based approach.  
Once a query has been defined, logic can be implemented to say “IF Matches = Fail, further due-diligence required”. IF NO Matches = Pass, and add record to On-going Monitor via API. There needs to be an element of accountability required for matches above the “threshold” where a compliance professional decides whether to on-board a customer and accept risk, discount false positives, or terminate the relationship with a customer. Therefore, the process can’t be automated fully.

How do we filter the API query by PEP position for local jurisdictions? i.e. In Italy how do we filter out lower level PEPs such as Mayors of small towns? 

There isn’t the ability currently to filter at a granular level such as by political position, or by sanction body. However, there is an element of post-response filtering that could be implemented using “PEP_Tier” or “Sanction_Body“. Using the example of lower-level Italian PEPs, there is a note on the profile referencing PILs – “Italian Public Administration”. For other jurisdictions, you can use the “PEP_Tier” and “Country” to filter out. All of the PEP Tiers mapped to the political position is available in Acuris Editorial Content Guide. 

Where is the API hosted?

Both are based in London (Equinix and Powergate)