Entity screening
Use business and related-party identifiers appropriate to the configured screening scope.
THIRD-PARTY SCREENING API
Bring AML and adverse-media signals into review.
Connect screening to supplier onboarding and ongoing review while keeping potential matches, source context and final decisions with authorised reviewers.
Built for server-side integration · Structured outcomes · Human-controlled decisions
OVERVIEW
A verification signal that fits the process.
Use the API result inside the workflow, evidence rules and approval responsibilities your organisation has defined.
Source context
Present potential risk and adverse-media signals with enough context for reviewer assessment.
Human decision
Keep possible matches separate from confirmed findings and documented approval decisions.
INPUTS
Start with the evidence you already collect.
1
Legal identity
Submit the business or person identifiers required for the authorised screening purpose.
2
Match context
Include available country, date or ownership context to help distinguish similar names.
3
Review event
Associate the request with onboarding, renewal, monitoring or an event-driven reassessment.
INTEGRATION NOTES
Designed for a controlled backend workflow.
- Designed for secure backend integration into onboarding and ongoing third-party review.
- The consuming application should preserve possible-match, no-match, review and technical-error states.
- List, media-source, jurisdiction and response-field coverage are confirmed during API onboarding.
A possible match or adverse-media item is not proof of wrongdoing. Confirm identity, source, relevance and applicable obligations before taking a decision.
WORKFLOW
From API call to documented decision.
Screen
Call the API from your backend using the identifiers approved for the review.
Triage
Route potential matches and adverse-media signals with their source context to the right reviewer.
Document
Record the reviewer conclusion, escalation and next action under the applicable policy.
RESPONSIBLE AUTOMATION
Automate the check.
Keep people accountable.
Vendoreye helps place verification evidence and exceptions in the right workflow. Your authorised team remains responsible for policy, escalation and approval.
Discuss your verification flow ↗Recommended decision states
- Check completed and evidence available
- Review required for a mismatch or possible match
- Evidence unavailable or insufficient
- Technical error requiring retry or support
Do not convert an unavailable check or technical error into a pass.
FREQUENTLY ASKED QUESTIONS
Questions teams ask before integration.
Does a potential match mean the supplier failed?
No. A potential match requires identity resolution and contextual review by an authorised person.
Can adverse media be used without human review?
It should not be treated as an automatic rejection signal. Review source quality, date, relevance and outcome.
Is one onboarding check enough?
Monitoring frequency should follow the applicable obligations, risk, ownership changes and your organisation's policy.
RELATED VERIFICATION APIs
Connect the checks your policy requires.
Use each result as evidence within a risk-based onboarding, renewal or change-control process.
VERIFICATION, CONNECTED
Bring the API into your
vendor workflow.
Tell us which checks, systems and approval stages you need to connect.
Request API access ↗