> For the complete documentation index, see [llms.txt](https://docs.parqex.com/-MUyxAVrX9S4wky8UoX6/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parqex.com/-MUyxAVrX9S4wky8UoX6/the-basics/testing-accounts.md). # Testing Accounts ### Using a Physical Device If you are building against the ParqEx Access+ Controller, you may request a physical sample be sent to you for testing. Please note, if your request is approved, it will take several days to receive the sample unit. To get started quickly, see the *Using the Simulator* section below. If you would still like a sample unit, please email with your name, the company you represent, and full address. ### Using the Simulator The ParqEx Account Simulator can be used in place of a real ParqEx Access+ Controller and is functionally indistinguishable from the perspective of the ParqEx Access+ product. You can request an unlimited number of testing accounts for your organization by emailing . These test accounts allow you to use the iOS/Android mobile apps, as well as the web dashboard. Since it is a full-fledged account, you can also use it to test Beam's other 3rd-party integrations, such as IFTTT and Amazon Alexa. --- # 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.parqex.com/-MUyxAVrX9S4wky8UoX6/the-basics/testing-accounts.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.