> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/connectors/connectors/makula.md). # Makula makula.io ### Authentication Makula uses 2 tokens. One short lived and a refresh token. When the short-lived token expires. Makula checks the validity of the refresh token and refreshes both tokens if it is valid. Expiration is: * Short-lived token: 6 minutes * Refresh token: 7 days Both tokens are sent from the client to the server. Server send tokens to the client only after login or if they get refreshed. Base domains: * Production * Staging ### Manipulating requests #### 1. Pagination Makula uses filter on queries with skip and limit like MongoDB. #### 2. Sorting One can sort by multiple fields. #### 3. Filtering Filtering works with: sort, skip, limit, ne, gt, gte, lt, lte, in, nin, contains, matches ### Further information Makula uses roles and permissions that are not documented on the API endpoints yet. For example only certain roles can perform specific queries or mutations. --- # 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.locoia.com/connectors/connectors/makula.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.