> For the complete documentation index, see [llms.txt](https://docs.ventiapp.mx/ventiapp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ventiapp.mx/ventiapp/english-api/developers/consideraciones.md). # Considerations ### Warnings There are API's to control Stock and Prices, the developer must be aware that he will work with data and sensitive information for the company. Ventiapp is not responsible for any poor implementation of APIs that are available and open to the user. ### Sandbox Ventiapp doesn't have an exclusive sandbox environment, but it does have specific test accounts where the developer will be able to carry out all their tests, including connecting to the channels they need in test accounts for each channel. To access these types of accounts, the developer must be part of a company that has acquired the services of Ventiapp. Access must be requested from indicating for which company it is developing. ### Production To move the developments made to production, the test account must be replaced with an Administrator account within Ventiapp, the recommendation is to make a new user specifically for the use of the API's since the information of the events carried out is stored in our logs. ### Limitations The Ventiapp API doesn't support having repeated SKUs in the products, this means that if the user has repeated SKUs and performs an update from the API, it will only take the oldest product that contains the SKU in question. --- # 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.ventiapp.mx/ventiapp/english-api/developers/consideraciones.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.