Adverse media search API

Find relevant adverse media.
Keep the evidence attached.

AdverseSearch turns a person screening request into a structured, source-backed response for business systems. No manual review queue.

Try the playground View the API

Asynchronous workflow Source-backed findings Clear limitations

screening_result.jsonCOMPLETED

{
  "id": "0194d6b4-b7d0-7ce4-a9c8-6f2b3c24a281",
  "status": "completed",
  "outcome": "potential_match",
  "failureCode": null,
  "coverage": {
    "complete": true,
    "searchesCompleted": 6,
    "sourcesReviewed": 11
  },
  "findings": [{
    "category": "regulatory",
    "eventStage": "enforcement",
    "severity": "high",
    "title": "Reported regulatory enforcement",
    "summary": "A cited source reports an enforcement event for the screened name.",
    "eventDate": null,
    "identity": {
      "confidence": "high",
      "matchedAttributes": [
        "dateOfBirth", "country"
      ],
      "conflictingAttributes": []
    },
    "adverseRelevance": "high",
    "sources": [{
      "title": "Regulatory notice",
      "url": "https://news.example/notice",
      "domain": "news.example",
      "publishedAt": null,
      "excerpt": "Example source evidence."
    }]
  }]
}

Evidence includedPOST /api/v1/screenings

Designed forCompliance operationsCustomer onboardingVendor screeningRisk platforms

One response, clear context

Screening signals your team can inspect.

Adverse media is rarely a simple yes or no. The response keeps source coverage, identity support, event stage, and uncertainty visible.

Broader search coverage

Use several focused search paths and pages for each subject, with clear coverage status in every response.

Identity evidence kept separate

See which details support a match and which details conflict, instead of receiving an unexplained score.

Sources attached to findings

Every accepted finding includes links and short supporting excerpts from the pages that were reviewed.

Built for workflow scale

Create asynchronous checks, poll a stable status resource, use idempotency keys, and track workspace usage.

Request to response

A simple API flow for a difficult search.

Start with the identifiers you have. Optional fields help distinguish people with the same name.

Read the developer guide

Send the subject

First and last name are required. Add DOB, location, phone, email, or other optional identifiers when available.

We search and verify

The service discovers candidate pages, reviews source content, and separates identity evidence from adverse relevance.

Receive a structured result

Use a stable outcome, findings, coverage, limitations, and source evidence in your own review workflow.

Purpose-built outcomes

No forced green light.

The API uses outcomes that preserve uncertainty: potential match, no verified matches, inconclusive, or search incomplete. A missing result is never presented as proof that a person is safe.

potential_matchno_verified_matchesinconclusivesearch_incomplete

Free check for eligible visitors

Test the full request shape.

Use fictional or authorized test data in the public playground.

Open playground

Find relevant adverse media.Keep the evidence attached.