> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/developer/api-integration/best-practices.md). # Best practices ## Gettings started When building integrations with different technologies and features, there are often multiple ways to achieve the same result. While many approaches may work, some can introduce unnecessary complexity or friction for the user. This can lead to issues such as: * Reduced usability * Harder maintenance over time * Unexpected behavior as the app evolves Following a set of best practices helps ensure a smoother user experience and more robust integrations. The guidelines below are recommended to help you get the most out of Struct PIM now and as your setup grows. ## Use of API The API is build for updating and reading large amounts of data in short time. All areas has extended support for batching data together to make the updating as smooth as possible. We do not recommend using the API as a direct source for presentation if performance is the main focus. \ You should always transfer the data needed for presentation, from the API, to a fast read and search friendly cache layer. This ensures optimal performance at all times. --- # 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.struct.com/developer/api-integration/best-practices.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.