> For the complete documentation index, see [llms.txt](https://developer.textmaster.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.textmaster.com/integrations/akeneo.md). # Akeneo Learn how our Akeneo integration works [TextMaster](https://app.textmaster.com/), is designed to seamlessly integrate with [Akeneo's Product Information Management](https://www.akeneo.com/) (PIM) system, acting as an efficient bridge between the two platforms. Utilizing a specially designed middleware connector, TextMaster harnesses the power of its APIs to streamline the translation process of your product information. With TextMaster, you can effortlessly send product translation requests directly from your Akeneo instance. The connector ensures the requests are properly transmitted, retrieves the source content, and initiates a new translation project within TextMaster. Once the translation is completed, the connector diligently monitors for finished projects. It promptly identifies these newly translated materials and ensures they are automatically imported back into your Akeneo instance. This ensures a consistent and efficient content flow, eliminating the need for manual data transfers. In essence, TextMaster not only enhances your product translation workflow but also enriches your product and product model data directly within the Akeneo platform. This integration bridges the gap between content management and translation, creating a cohesive and streamlined product information management process. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.textmaster.com/integrations/akeneo.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.