> For the complete documentation index, see [llms.txt](https://docs.lhv.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lhv.com/home/connect/fundamentals/environments.md). # Environments LHV Connect provides both a Live and a dedicated Prelive testing environment. Like the Live environment, Prelive features distinct connection certificates, payment accounts, and grants access to all or most of the same services and features. #### Live Environment The Live environment's base URLs are as follows: * **LHV UK**: `https://connect.lhv.com/` * **LHV Estonia**: `https://connect.lhv.eu/` #### Prelive Environment The Sandbox test environment is freely accessible for testing purposes. It can be utilized to test your integrations during the onboarding process or for any subsequent developments. Technically, it is very similar to the Live environment, with identical services, message structures, etc. * **LHV UK**: `https://connect.prelive.lhv.com/` * **LHV Estonia**: `https://connect.prelive.lhv.eu/` This structure allows you to seamlessly transition from testing to production, ensuring that your integrations are fully functional and reliable before going live. --- # 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.lhv.com/home/connect/fundamentals/environments.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.