> For the complete documentation index, see [llms.txt](https://api-docs.urbanpiper.com/downstream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.urbanpiper.com/downstream/authentication/authentication.md). # Authentication We use a static token-based authentication for all the requests made to our system via API calls. You must have already received the token which you would use in staging. This token will not change over a period of time and you can continue to use the same for all the requests. If at any point in time, you feel that the token you have been using has been compromised, please inform `pos.support@urbanpiper.com` immediately and request a new token. The above flow holds good for any single business entity you wish to onboard (with as many stores) through the integration. However, if you wish to onboard any businesses which support a multi-business model (commonly seen with cloud kitchens) please get in touch by sending an email to the aforesaid email id before implementing the integration. --- # 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://api-docs.urbanpiper.com/downstream/authentication/authentication.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.