Hi @satom ,

Thank you for reaching out to us!

Yes, your understanding is correct POST /cases/{caseSystemId}/screeningRequest result sets of this endpoint will have exact response as result response of endpoint GET/cases/{caseSystemId}/results.

you can go through below documentation for more information.

LSEG World-Check One API

Hope this helps!

Thanks

Vivek Pandey

Hi @Pandey Vivek ,
Thanks for your answer.
I understand that the results from the POST /cases/{caseSystemId}/screeningRequest endpoint will exactly match the response from the GET /cases/{caseSystemId}/results endpoint. Similarly, the cases from the POST /cases/{caseSystemId}/screeningRequest endpoint will have the same response as the case response from the GET /cases/{caseSystemId}?aggregatedSummary=true endpoint, correct?

Thanks
satom

Hi @satom,

please find our response below .

POST /cases/{caseSystemId}/screeningRequest with this endpoint you can expect detailed response of matches like if any entity got 10 matches its response will have record details of all 10 matches however with endpoint GET /cases/{caseSystemId}?aggregatedSummary=true its response will have just high-level overview of those records like it will show results as 10 matches however it will not have any detailed information of those records even it will not show records id it will just show those matches records are from which category.

Thanks

Vivek Pandey

Hi @Pandey Vivek ,
Thank you for your message.
You mean the two responses of getting case have difference, don't you?
However I have compaired response GET cases/{caseSystemId} with case of `{caseSystemId}/screeningRequest`. API reference is written same information. I couldn't find difference.
By the way, I needs the parrameters below. So in case of getting thease parameters, that two cases is same, isn't it?

• .case.lastScreenedDatesByProviderType.[]
• .case.creationDate
• .case.caseScreeningState.[WATCHLIST]
• .case.aggregatedResultSummaries.watchlist.watchlistReviewRequired
• .case.aggregatedResultSummaries.watchlist.watchlistUnresolved

thanks
satom

Hi @satom,

Thanks for reaching out!

As i have said earlier both endpoints will have same high level details however you will get detailed results with {caseSystemId}/screeningRequest endpoint.

So coming to your question about those five parameter.

for these three parameter in both endpoints you will have same details.

• .case.lastScreenedDatesByProviderType.[]
• .case.creationDate
• .case.caseScreeningState.[WATCHLIST]

however these two below parameter is only available with GET cases/{caseSystemId} endpoint.

• .case.aggregatedResultSummaries.watchlist.watchlistReviewRequired
• .case.aggregatedResultSummaries.watchlist.watchlistUnresolved

hope its clear now.

Thanks

Vivek Pandey

Hi @Pandey Vivek ,
Thank you for your explanation. However, I still haven't fully understood the details.
The API Document cases/{caseSystemId}/screeningRequest indicates the response has `case` and `case` has `aggregatedResultSummaries` and that two parameter.

You mean "Although it's not written in the API Documentation, these two parameter is not available". Is that understanding correct?

thanks
satom

Hi @satom ,

Can you please let us know your availability for Monday so that we can schedule call and try to clear your doubts.

Kindly provide us your email so that we can schedule call.

Thanks

Vivek Pandey