> For the complete documentation index, see [llms.txt](https://api-docs.myhappyforce.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.myhappyforce.com/docs/welcome.md). # Welcome Welcome to the Happyforce API documentation This API offers you the opportunity to integrate with Happyforce, enabling you to extract data and manage various aspects of your account. It's important to note that this API has been crafted and thoughtfully designed based on feedback and requests from our valued customers. Hence, we encourage you to reach out to us without hesitation for any suggestions, improvements, or new features you envision. We genuinely embrace your ideas and suggestions, as they play a pivotal role in guiding the growth of this API. Feel free to get in touch with us, as we eagerly look forward to collaborating with you to make this API even more robust and responsive to your needs. --- # 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://api-docs.myhappyforce.com/docs/welcome.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.