For a deeper look into our World Check One API, look into:
Hi,
I'm attempting to turn on ongoing screening for a newly created case as follows:
Call Cases to create the case
Call ScreeningRequest
Call OngoingScreening
Call Results
Without making the call to OngoingScreening I can poll the audit for the SCREENED_CASE entry and get a response within the usual 1-2 seconds timeframe.
If I DO call OngoingScreening then the polling of the audit never seems to complete.
Is there any best practice for turning Ongoing Screening on for a case?
Thanks
The call to screening is asynchronous and you should wait for it to complete before making another request for the same case.
Brian
Hi @stephen.davidson,
Is there any best practice for turning Ongoing Screening on for a case?
You can check with Postman the Ongoing screening returns status 204 and does not return message.
Hope this helps.
Thanks
Rakesh
Hi Rakesh,
Thanks for getting back to me - the question was more about the lack of a SCREENED_CASE entry in the audit when I call OngoingScreening after ScreeningRequest - is there any reason why calling OngoingScreening prevents this entry in the audit? As I mentioned, I poll the audit before I call Results.
If I call Cases => ScreeningRequest => wait for SCREENED_CASE in audit => Results I get results as expected
If I call Cases => ScreeningRequest => OngoingScreening => wait for SCREENED_CASE in audit then nothing seems to happen.
Thanks
Thanks, I'm now checking for SCREENED_CASE in the audit before attempting to call OngoingScreening.
