For a deeper look into our World Check One API, look into:
Hello,
Is it possible to have all the information included in the case report. we can have from the Web based WC One concerning a case (see attachment). If yes, what is the requests one should combine to have the same informations.
Best Regards
Nabil
You can combine the below API calls to create the report.
1. Sync Screening request API
2. Screening result API call
3. Fetch full case details API call.
4. Audit event API call.
For the field "World-Check Total Matches", you can use the Screening result API call or Sync Screening request API call to fetch the total number of resultIds, the final count of resultIds can be World-Check Total Matches.
For the fields, "Name", "Case ID". "Current Group","Case Created", "Ongoing Screening", "Name Transposition", "Entity Type", "Archived"- you can use the "Fetch full case details" API call.
For the field "Last screened", please use "Audit Event API" and check for the actionType: SCREENED_CASE and pick up the one that has the latest value of "eventDate" in it (if the case has been initially screened multiple times).
For the section "Key Findings", you can use the Screening result API call (cannot use sync screening as it does have resolution status details in it) to populate all the fields.
For the section "WORLD-CHECK MATCHES", let me elaborate field by field.
Resolution Status-Screening result API call
Matching Entity -Screening result API call or sync screening API call.
WC UID -Screening result API call or sync screening API call.
Type -Screening result API call or sync screening API call using the attribute "categories".
Category - Sync Screening API call using the attribute "category"
Gender -Screening result API (if the client has passed secondary identifiers while screening) other wise Sync Screening API call
Date(s) of Birth-Screening result API (if the client has passed secondary identifiers while screening) other wise Sync Screening API call
Nationality-Screening result API (if the client has passed secondary identifiers while screening) other wise Sync Screening API call
Location-Screening result API (if the client has passed secondary identifiers while screening) other wise Sync Screening API call
Resolved on -Screening result API call
Risk Resolution -Screening result API call
Reason -Screening result API call
Resolution Comment -Screening result API call
Match Strength-Screening result API call or Sync Screening request API.
For the section "Audit", you can use the audit event API call.
