# Translations

For each individual requests it's possible to set the language using the "Accept-Language" header. Here are some examples:

* Error/Warning/Info Messages support language translations with Accept-Language header. Returned response header contains the base64 encoded string.

<figure><img src="/files/i5lSBWEEjWkUBXGFg2PW" alt=""><figcaption><p>Request</p></figcaption></figure>

<figure><img src="/files/N36NBTfyqtK1P8ruCKB3" alt=""><figcaption><p>Response</p></figcaption></figure>

* Basic data translations are supported with Accept-Language header. Returned response body contains the translated text for Block Reason Description.

<figure><img src="/files/mNNDbdph3wjhTmAhocfQ" alt=""><figcaption><p>Basic data translations</p></figcaption></figure>

<figure><img src="/files/7EvcZGnjtGyWTfOxYrUq" alt=""><figcaption><p>Response</p></figcaption></figure>

###

### Custom Enumerations and their translations

TODO


---

# Agent Instructions: 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:

```
GET https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/implementation/translations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.