Case Management and Audit - V2
Overview
The Case Management and Audit variant of World-Check One API enables clients to screen names and securely store case and match information within the World-Check One infrastructure, along with a full audit trail. This information can be accessed, modified, or deleted at any time either via the API or the Desktop interface. Cases can also be set to Ongoing Screening, allowing automated screening for Risk Intelligence updates.
Workflow
There are 2 typical workflows for the Case Management and Audit variant:
-
Full API integration:
-
Cases are created via the API
-
Case details are accessed via the API for review, investigation, and remediation
-
Ongoing Screening or re-screening are triggered via the API
-
Case lifecycle operations are done via the API, such as archiving and deletion
-
Group configuration and other Admin-related functions are done via the WC1 Desktop
-
-
Hybrid API integration:
-
Cases are generally created via the API integration
-
Cases may also be created via the WC1 Desktop
-
Investigation, remediation, setting of OGS, or re-screening are done via the WC1 Desktop
-
Case lifecycle operations are done either via the API or WC1 Desktop, such as archiving and deletion
-
Group configuration and other Admin-related functions are done via the WC1 Desktop
-
- Workflow UML interaction diagrams - V2
-
Refer to these UML activity and sequence diagrams to understand the expected workflow when dealing with the various World-Check One API methods.
Zero-Footprint Screening
Screening without permanently storing the case data, matches, and audit information is provided within the Case Management and Audit variant of WC1 API. This is achieved by creating one or more Groups specifically configured for ZFS screening. All names and screening results against such groups will not be saved.
Sample Use Cases
- Sample API HTTP requests (Postman Collection) - V2
-
Refer to this link for sample API requests in HTTP format, provided as a Postman collection. This collection outlines the sequence of API methods required to perform a KYC/AML screening workflow and provides some example HTTP requests for each method to illustrate how to integrate with the API. Import the World-Check One API - V2 environment file to allow full interaction with the World-Check One API environment with this Postman collection. The environment file can be used for both Pilot and Production accounts.
PLEASE NOTE: The Google Chrome version of Postman and the accompanying Interceptor plugin are now deprecated. Please use the native version of Postman. The Interceptor is no longer required.
Schema Reference
- Security and Authentication details - V2
-
Refer to these guides for requirements around security and authentication when interacting with the World-Check One API.
- API Schema Reference Documentation - V2
-
This provides detailed reference for all methods supported by the World-Check One API, together with all associated data models. This documentation is generated from the Swagger schema (linked below) and is provided as a more convenient way to navigate the detailed API reference material. Users are free to utilise the schema itself to derive an alternative representation for their own reference purposes.
- Swagger API Schema - V2
-
The World-Check One API schema, in Swagger format. Developers can use this to work with existing tools within the Swagger development ecosystem, for example to generate API clients in their language of choice. Requests made to the World-Check One API must adhere to the format outlined in this schema in order to be successfully processed.
Appendix A: Copyright
(c) 2018 - 2023 LSEG. All rights reserved. Republication or redistribution of LSEG content, including by framing or similar means, is prohibited without the prior written consent of LSEG. 'LSEG' and the LSEG logo are registered trademarks and trademarks of LSEG and its affiliated companies.