Integrate AML screening directly into your stack.
The BriteBase screening API is a self-serve delivery option for engineering-led teams: embed sanctions, PEP and adverse-media screening into onboarding, customer monitoring or payment flows, with structured responses and low implementation friction.
One call in, a structured decision back.
Real-time screening
Send a customer, company or payment and get a structured decision back in the same request, not a batch job you poll later.
One entity-resolution engine
Sanctions, PEP and adverse-media matching all run through the same resolution logic, so the noise reduction and rationale format are consistent across every check.
Structured, explainable responses
Every hit carries a plain-language rationale and a risk signal breakdown, not just a bare match score, so your team can act on the response without a second lookup.
API-key authentication
Every request is authenticated with a key issued to your account when you get access. No shared credentials, no unauthenticated endpoints.
Four steps from access to an audit-ready record.
Get API access. Book a demo or contact us and we will provision a key and walk through the integration with your team.
Send a screening request. Pass the entity you are screening, a customer, a company, or a payment party, in a structured request.
Receive a structured decision. The response carries the match outcome, a risk signal breakdown, and a plain-language rationale for any hit.
Record the disposition. Push your team’s decision back so it lives in the same audit trail as the original screening call.
Illustrative, not a full reference.
The example alongside shows the general shape of a screening call and response, an entity in, a decision with a rationale out. Exact endpoints, fields and authentication details are shared directly with your team once you have API access, so this page stays a starting point rather than out-of-date reference documentation.
- Sandbox access for integration testing before go-live
- Engineering support during integration, not a self-serve-only handoff
POST /screen
{
"entity_type": "individual",
"name": "Caspian Trade Group",
"jurisdiction": "CY",
"checks": ["sanctions", "pep", "adverse_media"]
}
200 OK
{
"result": "review",
"risk_score": 35,
"hits": [
{
"list": "pep_tier_2",
"rationale": "Name and role match against
a tier-2 politically exposed person
record.",
"disposition": "pending"
}
]
}Developer FAQ
Is the API self-serve, or do I need a sales call first?
Access itself is self-serve once your account is provisioned. We ask every new integration to talk to engineering first, not as a sales gate, but because a short call surfaces the entity types and volume you are screening, which shapes how you should structure requests.
Does the API cover ongoing monitoring, or only point-in-time checks?
Both. A screening call at onboarding is a point-in-time check; entities can also be enrolled for ongoing monitoring, so new matches surface for disposition as lists and risk profiles change, without a separate polling job on your side.
Can I use the API alongside the case-management platform?
Yes. The API and the unified compliance platform share the same entity-resolution engine and the same underlying data, so a team can integrate screening directly into their product via the API while compliance operations works alerts and investigations in the platform, with one consistent audit trail across both.
Get API access and a walkthrough with engineering.
Book a demo and we will provision access, share the full endpoint reference, and help you scope the integration.