> For the complete documentation index, see [llms.txt](https://docs.hos.accessacloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hos.accessacloud.com/epos-api-reference/readme.md). # Access EPOS API Documentation ### About The Access Group The Access Group is one of the largest UK-headquartered business software providers, founded in 1991 and employing over 7,500 people. The company serves more than 100,000 organisations across the UK, Ireland, US, and Asia Pacific. Our technology portfolio includes enterprise-grade solutions for finance, HR, payroll, payments processing, and sector-specific business management systems. Built on cloud infrastructure, our Access Evo platform leverages AI to deliver integrated software experiences across multiple business functions. As an integration partner, you'll benefit from our extensive ecosystem of connected services and our commitment to open APIs that enable seamless data exchange between systems. ### Access EPOS Platform Overview Access EPOS is an enterprise hospitality point-of-sale platform with over 30 years of development history, deployed across 3,000+ venues including restaurants, bars, pubs, and hotels. The system is built to support high-volume transaction processing whilst maintaining reliability and performance in mission-critical hospitality environments. --- # 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://docs.hos.accessacloud.com/epos-api-reference/readme.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.