Content API webUrl domain issue (.com links not reachable)

[Vladislav Yatsenko]

Hello Tripadvisor Content API Team,

We are integrating your Content API (specifically the Get Location Details endpoint), and we are encountering an issue with the webUrl field.

The API returns URLs with the .com domain, for example:

• https://www.tripadvisor.com/Hotel_Review-g295424-d23898397-Reviews-Hyatt_Place_Dubai_Jumeirah_Residences-Dubai_Emirate_of_Dubai.html
• https://www.tripadvisor.com/Hotel_Review-g298251-d1723972-Reviews-Rixos_Almaty-Almaty.html
• https://www.tripadvisor.com/Hotel_Review-g295424-d301525-Reviews-Regent_Palace_Hotel_Dubai-Dubai_Emirate_of_Dubai.html

These links are not reachable from our region (Kazakhstan) and return “This site can’t be reached”.

However, when accessing the same hotels via Tripadvisor search, the working pages are served under the .ru domain, for example:

• https://www.tripadvisor.ru/Hotel_Review-g295424-d23898397-Reviews-Hyatt_Place_Dubai_Jumeirah_Residences-Dubai_Emirate_of_Dubai.html
• https://www.tripadvisor.ru/Hotel_Review-g298251-d1723972-Reviews-Rixos_Almaty-Almaty.html
• https://www.tripadvisor.ru/Hotel_Review-g295424-d301525-Reviews-Regent_Palace_Hotel_Dubai-Dubai_Emirate_of_Dubai.html

We also tested adding anchors (e.g. #REVIEWS), but the issue persists regardless.

Could you please clarify:

1. Is this expected behavior for the webUrl field in certain regions?
2. Should we rely on the .com domain as canonical, or adapt it to a region-specific domain (e.g. .ru)?
3. Is it acceptable (and compliant with your Content API policies) to programmatically replace the domain (e.g. .com → .ru) to ensure accessibility for users?
4. Alternatively, is there a recommended way to obtain region-aware or localized URLs from the API?

We want to ensure compliance with Tripadvisor guidelines while maintaining working links for our users.

Thank you in advance for your guidance.

Best regards,
Vladislav