Hi @mark.kalgren

Thanks for reaching out to us!

We had tried initiating the Ongoing screening request using your (Mark.Kalgren@am.jll.com) pilot credentials and we were able to successfully enable the OGS.


So, we request you to make sure that you are using the valid casesystemId in your URL to enable the OGS. As 404 error may have triggered due to variety of reasons such as "due to invalid casesystemId" "may be the case was already deleted" etc.

Please note: CaseSystemID is totally different from CaseID

Since you are using the v1 you will get only caseID in the ScreeningRequest response,so in order to get the CaseSystemID you will have to initiated "SEQ-case-retrieve: Get the system ID of a case". Post that you can utilize that CaseSystemID to enable OGS.

Please feel free to reach out to us if you have any additional questions.

Thanks
Vivek Kumar Singh

I see you are using the v2 version of the API - do I need to switch to that in my application for this to work?

I am also receiving a 404 when making a call to get the system ID of the case (5jb6bljoav941gdrnay12ewe7, production not pilot).

Further, for my internal records, when was this changed? We have been using the ID returned from the ScreeningRequest call in this application since 2018 without any issue.

Hi @mark.kalgren

We would like you to please let us know the best available time so that we can schedule a session to discuss this issue in detail.

Thanks
Vivek Kumar Singh

I am available today for the next 8 hours. My normal working hours are 8:00 AM - 5:00PM Eastern time. I am also available at the same time on Monday,

Hi @mark.kalgren

We had sent you an invite, now, we are waiting for you to join the session.

Thanks
Vivek Kumar Singh