# Localization

Suppliers can store content in multiple languages in Ventrata. Requests should include the `Accept-Language` [header](https://docs.ventrata.com/getting-started/headers), ideally matching the language preferences sent by the client browser or user agent.

More information about the structure of that header is available on [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language).

The API attempts to match the preferred languages against languages already translated by the supplier. The response includes a `Content-Language` header indicating the language returned, consistent with the HTTP standard.

Use the product operation below with the `Accept-Language` header to request localized content:

{% openapi src="<https://221588849-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M7bgGIyO7QYNOfUMfxh%2Fuploads%2Fgit-blob-fa2d8cb1d7297d352c2639e6c4c6a990f2add6d7%2Fopenapi.yaml?alt=media>" path="/products/{productId}" method="get" %}
[openapi.yaml](https://221588849-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M7bgGIyO7QYNOfUMfxh%2Fuploads%2Fgit-blob-fa2d8cb1d7297d352c2639e6c4c6a990f2add6d7%2Fopenapi.yaml?alt=media)
{% endopenapi %}

The response `Content-Language` reflects the resolved language (for example English when no other translation exists):

If you cache content locally, use the `Octo-Available-Languages` header, which lists languages translated by the supplier.

You can repeat the request with each available language to retrieve localized content.