question

Upvotes
Accepted
Sugam Surve avatar image
24 ●2 ●5 ●9

World Check One API Case Screening Access Forbidden from offshore location

We have developed World check one screening integration recently in production with OGS on. Now we are planning to call async APIs for screening with OGS off. When our offshore developers started working on changes, they faced issues in screening request while executing code from offshore machine (India location). Same code works from machine in US location. You can refer screenshot of error attached below that shows jasonResponse with Access Forbidden error.

Any idea what could be issue for offshore developers? Let me know if any additional information is needed on this. We noticed difference in dataToSign when code is executed from offshore location Vs location in US. Not sure if that could cause any issue. Could this be related to pilot account provided to us?

Any help of this is highly appreciated.

wc1-error.jpg

Thanks,

Sugam

world-checkworld-check-oneauthentication
wc1-error.jpg (191.0 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
Prabhjyot avatar image
4.5k ●4 ●8 ●8

@Sugam Surve,

Thank you for your query.

The URL in the provided screenshot seems to be pointing to the pilot environment and could be the cause of the API call failure. Can you please provide us the response and the request headers for the failed API call from onshore and offshore systems to take a look into it?

Also, if you are facing issue with the production environment, please raise the issue via the support channel. Please find the instructions in the following link -

https://community.developers.refinitiv.com/questions/40602/i-am-facing-issue-with-the-world-check-one-api-pro.html

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.