Hi @tim.loh,

There was no service disruption that would have caused you to see 404 Not found.

The screening result API would return 404 if you have passed an incorrect CaseSystem ID while fetching the screening result!

Can you please check if there was any change in caseSystem ID which you used while fetching the result around the time that you have mentioned?

Also please note if there are no matches to your screened case you would just get a 200Ok with a blank response!

Let me know if you need further information on this!

Thanks,

Mehran Khan

API Technical Consultant

Hi @Mehran.Ahmed Khan,

Our system is running a cron job that will call the World Check One API every 5 minutes to check if a particular case has been fully resolved manually. Based on our logs, the api calls to retrieve the results were successful from the case screen time (2018-10-02T12:31:17) until the first error (2018-10-02 17:08:26). The CaseSystemID was not changed when we fire the api calls. That's the reason why we thought it was a service disruption on your end.

Are there any other possibilities from your end that might have caused the result to return 404?

Hi @tim.loh,

Can you please send across complete request response for which you received 404!

The reason I'm ruling out service disruption is cause that would probably give you a 500 server error not 404.

Please provide me the complete request and response along with the headers so that I can investigate further!

Regards,

Mehran Khan

Hi @tim.loh,

Just to add to my previous comment, I did a thorough investigation and can confirm that there was no service outage during the above mention date/times, also there were no issues reported by any other customers, I would like you to reach out to our support team GRC.WC.Support@thomsosnreuters.com who should be able to assist you further on this!

Hi @Mehran.Ahmed Khan,

I will send an email to GRC.WC.Support@thomsosnreuters.com to ask for further assistance.

Thanks!