# Localization ## Language Variants If a resource has multiple language variants and the difference between variants is only in the language of human-readable fields, then the [`Accept-Language`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language) request HTTP header **SHOULD** be used to select the desired language variant. ### Example ``` GET /article HTTP/1.1 Accept-Language: en,en-US,fr;q=0.6 ``` ``` HTTP/1.1 200 OK Content-Type: application/hal+json;charset=UTF-8 Content-Language: en Vary: Accept-Language ... ``` ## Language or Country-specific Data Structure If the difference between language or country specific variants of a resource is bigger than just in the content of human readable strings, for example, the data structure of the resource representation is different, then a query parameter **SHOULD** be used to communicate the requested variant. ### Example ``` GET /article?market=en_US HTTP/1.1 ``` ``` HTTP/1.1 200 OK Content-Type: application/hal+json;charset=UTF-8 Content-Language: en Vary: Accept-Language ... ``` --- # 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://adidas.gitbook.io/api-guidelines/rest-api-guidelines/execution/localization.md?ask= ``` 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.