> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/introduction/translation-tool.md).
# Translation Tool
In the Unified Odds Feed API, we offer a tool that enables you to enter your specific translations for the data provided via API. By default, you will receive our official translation for each language. However, if you would like to change the translations, you can do so using our new translation tool.
{% hint style="warning" %}
The translation tool must be enabled for you to access it. This can be done during the integration phase or later on request through your sales representative.
When making the request, please ensure you provide your **Bookmaker ID** and the **required language**.
Please note that the customer-specific translations are only available in the **production environment.**
{% endhint %}
### **Navigate To The Translation Tool**
The new **Translation Tool** is now available in the [**Betradar Portal**](https://portal.betradar.com/) at:
**Configuration → Translation Tool**
Depending on the type of translations you would like to update, select the related language (blue box) and the corresponding entity (black box). Within the related type, you can define the scope (purple) in more detail.
In the search window (green box), you can search for competitors, tournaments, and players. If you have previously chosen an entity, you can also select it by ID.
Please note that from now on, you can no longer use the old translation tool (via [betradar.com](http://betradar.com/)) to alter translations for the Unified Odds Feed API.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sportradar.com/uof/introduction/translation-tool.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.