Hi Support team,
I am using https://restapi-us2p.select.datascope.thomsonreuters.com/v1 as EndPoint to help clients to retrieve data from Java application. I am in China and it seems that thomsonreuters.com has been blocked by GFW as same with Google, Facebook.
The connection is always lost and I need to retry lot of times. Do we have any other domain URL (suffix by refinitiv.com) or IP which is for REST API? I tried IP in the document, but it seems that official IP in the document could not invoke REST API.
I agree with @veerapath.rungruengrayubkul but I guess this will still go with China GFW restriction process.
I checked further and in order to access Datascope you will need to use proxy IPs that should be set up locally by IT team. By this you will bypass the request of restricted domain access and proxy will help you connect these restricted domain. This what our customers too do when they have strigent IT policy in place, where they cannot white-list DSS hostname/IP.
Please get in touch with your local IT support and explain them the problem you are facing. I am sure they will have similar arrangement made for other demands.
Previously I had suggested few customers to use this below method but I just tried again but this did not work. I need to find PORT that is currently being used for DSS REST API.
REST API endpoints are still residing with Reuters.com domain, we can expect in future this will be migrated as well. You can press the need of today by Chinese GFW rule.
According to Product Suite Connection Options document, the REST API endpoint and IP is hosted.datascopeapi.reuters.com/RestApi/v1 and 220.127.116.11 respectively. Application may use IP instead. For example, https://18.104.22.168/RestApi/v1/Authentication/RequestToken.
However, the request might fail because of SSL certificate verification as domain name mismatch.
Are you able to use ping command to 22.214.171.124? What error is received on the Java application?
It is expected behavior to get SSL certificate error, when using IP address instead of hostname. You can disable SSL hostname verification on Apache HTTP client as workaround.
Below is the sample of code which can work with the Java Code Examples.
private CloseableHttpClient httpclient = HttpClientBuilder.create().disableContentCompression().setSSLHostnameVerifier(org.apache.http.conn.ssl.NoopHostnameVerifier.INSTANCE).build();
The Ping test is to just ensure that you can reach the IP.