Integrate ClearSanction screening into your workflow
Use the ClearSanction REST API to submit supported screening requests from your own systems and workflows rather than relying solely on manual Portal searches.
API screening uses the same core ClearSanction screening semantics, helping organisations keep Potential Match and Match Score meaning consistent across integrated and Portal-based screening.
Bring screening closer to the process that needs it
Manual Portal screening is useful for direct analyst searches. Some organisations also need screening to operate as part of an existing business or compliance process.
The REST API provides an integration route for supported screening requests so ClearSanction can be incorporated into those operational journeys.
When API integration may be appropriate
API integration may be relevant where an organisation wants to:
- check_circlesubmit supported screening requests from an existing application;
- check_circleincorporate screening into an onboarding process;
- check_circleconnect screening with an internal compliance process;
- check_circleautomate submission of supported screening requests;
- check_circlesupport operational screening volumes that are better handled through integration.
These are integration scenarios, not claims of pre-built connectors to specific systems.
Use the canonical screening model
The API is another way to access ClearSanction screening, not a separate screening engine.
Potential Matches and Match Score retain their approved meaning across Portal and API screening.
Choose Portal or API around the operating model
The Portal supports direct interaction with ClearSanction for user-led screening and review.
The API is intended for organisations that need supported screening requests to originate within their own systems or operational processes.
The choice is therefore about how screening is accessed and incorporated into the customer workflow, not a different definition of the screening result.
Evaluate the technical implementation in Docs
Authentication, endpoints, schemas, request and response examples, API keys, sandbox configuration, error handling and version-specific technical behaviour belong in the developer documentation.
Discuss integration requirements
The REST API is an enterprise-oriented capability. Organisations evaluating integration can discuss their operating model and requirements with ClearSanction.
Frequently Asked Questions
Does API screening use a different Match Score?
No. API and Portal screening use consistent canonical screening semantics. Match Score retains its approved meaning as the strength of identity correspondence.
Does ClearSanction provide pre-built ERP or CRM integrations?
No. ClearSanction does not provide pre-built ERP or CRM integrations. The REST API provides an integration capability that customers can use within supported implementation scenarios.
Where can developers find endpoint and authentication details?
The technical API documentation is available through /docs.
Take screening into your own workflow
Review the technical documentation to understand the API, or discuss your integration requirements with ClearSanction.