Bulk Search

AML Watcher offers a Bulk Search feature, enabling users to submit multiple search payloads in a single request. This enhancement streamlines AML compliance efforts by accelerating search processes and improving operational efficiency. With Bulk Search, users can efficiently screen customer transactions, conduct due diligence, and monitor for suspicious activities, enhancing risk detection capabilities while minimizing resource utilization.

Note: The Bulk Search feature offers a powerful capability, although it may not be available to all organizations by default.

Authorization: To use the Bulk Search API, users must provide an authorization token in their request headers. This token can be obtained from the Get Access Token endpoint, which authenticates and authorizes access to the Bulk Search feature.

Availability: Bulk Search availability is contingent upon organizational access privileges. If your organization requires access to this feature, please contact us at [email protected] to discuss enabling it for your account.

Limitations: In a single bulk search request, a maximum of 10 individual searches will be processed. This ensures optimal performance and resource utilization across the platform.

POST/api/bulk-search
POST https://api.amlwatcher.com/api/bulk-search HTTP/1.1
Host: api.amlwatcher.com
Content-Type: application/json
Content-Length: 1441
Authorization: Bearer Token

{
    "batch_name": "Batch 1",
    "api_key": "your-api-key",
    "callback": "Provide a webhook",
    "payloads": [
    {
      "name": "Donald Lu",
      "unique_identifier": "",
      "client_reference": "",
      "birth_incorporation_date": "",
      "country": ["PK"],
      "category": ["PEP Level 2"],
      "entity_type": ["Person"],
      "rca_search": false,
      "alias_search": true,
      "ongoing_monitoring": true,
      "adverse_media_monitoring": false,
      "match_score": 25
    }
  ]
}

Request

Parameters	Required	Type	Description
batch_name	Yes	String	The name of batch you want to create. Min: 2 character Max: 100 characters Constraint: Batch name should not consist entirely of special characters or numbers.
api_key	Optional	String	An API key is required to perform bulk search, only if access token is not passed in authorization header as a bearer token.
callback	Yes	String	A callback response upon job completion will be returned to the following URL.
payloads	Yes	Array	Array of multiple payloads with several cases.
name	Yes	String	The name of entity/business you want to search. Min: 2 character Max: 100 characters Constraint: Name should not consist entirely of special characters or numbers.
country	No	Array	Array of countries based on which you want to filters reports. See Countries. Note: ISO 3166-1 alpha-2 country codes are supported. Example: ["CA", "IN"]
category	Yes	Array	Array of categories based on which you want to filters reports. See Categories. Example: ["Adverse Media", "SIP"]
birth_incorporation_date	No	String	Date(DD-MM-YYYY) based on which you want to filters reports. Note: To perform year search you can use the format 00-00-1947 and vice versa for date, month or combination of the three. Example: 10-03-1947 \| 10-03-0000 \| 00-03-1947 \| 00-00-1947
unique_identifier	No	String	Unique identifier can be used to filter the search records. Min: 2 character Max: 50 characters Constraint: Unique identifier should not consist entirely of special characters. Note: It can be any key within the data object like Passport No, National ID number. Example: TR12345677.
alias_search	Yes	Boolean	Alias search is used to specify whether user want to perform search within aliases or not. Note: The default value of alias_search is True. Example: True.
rca_search	Yes	Boolean	RCA search is used to specify whether user want to perform search within rca or not. Description: RCA (Relatives and Close Associates) - Immediate family members or close social or professional contacts of a government or political official, or senior executive – meaning spouses, parents, siblings, children, and spouses’ parents and siblings. Note: The default value of rca_search is True. Example: True.
ongoing_monitoring	Yes	Boolean	Ongoing monitoring is used to monitor the cases for Ongoing AML. Note: The default value of ongoing_monitoring is False. Example: True.
adverse_media_monitoring	No	Boolean	Ongoing monitoring is used to monitor the cases for Ongoing Adverse Media. Note: The default value of adverse_media_monitoring is False. Example: True. Disclaimer: Please note that any Adverse Media Ongoing is monitored minimum at every hour.
entity_type	No	Array	Entity Type: AML screening serves the purpose of identifying individuals or entities listed in various AML databases. AML Watcher provides screening services of five types of entities i.e. Person, Company, Organization, Crypto_Wallet, Vessel and Aircraft. Example: ["Person"].
match_score	No	Integer	The match score determines the level of similarity required between the search term and the matched terms. A value of 0 allows for the loosest match, while 100 represents the closest match. Note: It ranges from 0-100. By default value is 80 Example: 65
client_reference	No	String	A unique client reference can be assigned to each search.

Response

Parameters	Description
error	Whenever there is an error in your request, this param will have details of that error; otherwise it’ll remain empty.
status	The status field is set to either “SUCCESS” or “FAIL”, indicating that the API request resulted in a successful or failure/error condition respectively.
data	An object containing status of batch search and batch ID.

Sample Response
{
    "data": {
        "batch_id": "cbcbb9dcba6b80618ok5af62",
        "status": "PENDING"
    },
    "error": false,
    "status": "SUCCESS"
}

Request​

Response​

Request

Response