Do we have static ip for the api.refinitiv.com

Frederic

Doe we have static IP bound to api.refinitiv.com? which can be used in firewall configuration instead of url

wasin.w

Hello @Frederic

Could you please clarify the "the IP of api.refinitiv.com always maps to other AWS endpoint URLs" statement?

I did a quick test with the IP 75.X.X.X and it works fine. My replication steps are as follow:

1. Get RDP Authentication from https://75.X.X.X/auth/oauth2/v1/token endpoint URL
2. Request ESG data from https://75.X.X.X/data/environmental-social-governance/v2/views/basic?universe=TSLA.O endpoint URL
3. Request Symbology lookup from https://75.X.X.X/discovery/symbology/v1/lookup

All HTTP request messages get data successfully.

Please contact the Sales team regarding the Delivery Connect pricing and how to get access.

Frederic

Many thanks
@wasin.w

The client encounters the issue that their DNS cannot map the IP to the same URL as "api.refinitiv.com" (will actually be mapped to some aws endpoint url), so they would like to have the IPs that can be configured in their firewall. Do you have some suggestions on the DNS / firewall configuration to mitigate this? Or some DNS configuration is required?

wasin.w

Hello @Frederic

Do you mean the client cannot map 75.x.x.x and 99.x.x.x IP Addresses to the api.refinitiv.com?

Frederic

yes yes, so their app network connection cannot pass their firewall configured with URL rules

wasin.w

Hello @Frederic

The 75.x.x.x. and 99.x.x.x IPs are the AWS Elastic IP which is the static IPv4 that can be accessed from the public internet.

Does the client has any firewall, network policies, or even in the region that blocks the public internet or Amazon AWS?

Please be informed that there is the Delivery Connect that lets the client connect to RDP via a private network as well.

Frederic

The client has firewall. Currently they configure the firewall with the api.refinitiv.com url, however, the ip of api.refinitiv.com always maps to other aws endpoint urls, so as a result their firewall still blocks the access.

Regarding the Delivery Connect option, is that free of charge and how to enable that?

Frederic

Thanks for the information.
The problem is the IP/URL accessed will be mapped to a397101cbd5c634c0.awsglobalaccelerator.com (or other AWS addresses) so it will be blocked by their firewall (not recognized as "api.refinitiv.com"). Any I think it would be client's DNS configuration problem. just would like to know if we have any experience on this?

wasin.w

Hello @Frederic

This is the first time I found this network issue in the Q&A forum. It might be something with the client DNS/network. I highly recommend you contact the RDP support team directly.