Adverse Media Screening
Risk & ComplianceFind negative news about a person or company across news and public sources.
Screen a name against news archives and public sources for fraud, financial crime, regulatory action, violence and other risk categories. Results are classified by category and relevance so compliance and HR teams review only what matters.
Endpoint
Request parameters
| Field | Type | Description |
|---|---|---|
name_individual_or_entity
required
|
string | Name (individual or entity) |
context_company_location_role
optional
|
string | Context (company, location, role) |
Example request
curl -X POST https://app.emver.io/api/sandbox/v1/adverse-media-screening \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"name_individual_or_entity": "string",
"context_company_location_role": "string"
}'
import requests
response = requests.post(
"https://app.emver.io/api/sandbox/v1/adverse-media-screening",
headers={
"Authorization": "Bearer YOUR_API_KEY",
"Accept": "application/json",
},
json={
"name_individual_or_entity": "string",
"context_company_location_role": "string"
},
timeout=60,
)
response.raise_for_status()
data = response.json()
const response = await fetch("https://app.emver.io/api/sandbox/v1/adverse-media-screening", {
method: "POST",
headers: {
"Authorization": "Bearer YOUR_API_KEY",
"Content-Type": "application/json",
"Accept": "application/json",
},
body: JSON.stringify({
"name_individual_or_entity": "string",
"context_company_location_role": "string"
}),
});
const data = await response.json();
$response = Http::withToken('YOUR_API_KEY')
->acceptJson()
->post('https://app.emver.io/api/sandbox/v1/adverse-media-screening', {
"name_individual_or_entity": "string",
"context_company_location_role": "string"
});
$data = $response->json();
Replace YOUR_API_KEY and the placeholder values. Use the switch above to see production URLs.
Response
Structure · 200
{
"status": INTEGER,
"message": STRING,
"data": {
"articles_found_with_source_and_date": STRING,
"risk_category_per_article": STRING,
"relevance_score": STRING,
"summary_of_allegations": STRING,
"monitoring_alerts": STRING
}
}
Example · 200
{
"status": 200,
"message": "string",
"data": {
"articles_found_with_source_and_date": "string",
"risk_category_per_article": "string",
"relevance_score": "string",
"summary_of_allegations": "string",
"monitoring_alerts": "string"
}
}
Error · 4xx / 5xx
{
"status": INTEGER,
"message": STRING
}
See Errors & status codes for what each status means and which calls are billed.
About this API
Sanctions lists lag behind the news. Adverse Media Screening searches mainstream and regional news, regulatory releases and public records for reports linking a person or entity to risk events, then classifies and de-duplicates them. It is the early-warning layer of a compliance programme.
Ongoing monitoring re-runs the search and alerts you when new coverage appears.
Typical uses
- Executive and board appointments. Reputation due diligence for leadership.
- Vendor and partner screening. Fraud and regulatory history of counterparties.
- Enhanced due diligence. High-risk customer reviews for AML programmes.
- Investment screening. Promoter and founder background.
Questions
- How are common names handled?
- Context such as company, location and role narrows matches, and each article carries a relevance score.
- Are regional-language sources included?
- Yes. Major Indian-language publications are covered alongside English sources.