> For the complete documentation index, see [llms.txt](https://docs.gantner.com/eloxx-365/HN3yXU2vWRZ8y5EuQtp8/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gantner.com/eloxx-365/HN3yXU2vWRZ8y5EuQtp8/developers/authentication-api/authentication-api.md). # Authentication API Authentication API is used for authenticating to the Enviso platform. Once an API key has been created and assigned to a tenant, the integrator will be able to make use of this API key to call the API endpoints. For each call used, you must add the headers for: * TenantKey: x-tenantsecretkey * Api key: x-api-key * JWT Access bearer Token: Authorization Each key will be used for its own purpose. * TenantKey: Identifies the tenant for which an API action will be performed. * API key: Identifies the integrator that is calling the API. * JWT Access bearer token: Serves as authorization and authentication token in order to perform an action on the API. --- # 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: ``` GET https://docs.gantner.com/eloxx-365/HN3yXU2vWRZ8y5EuQtp8/developers/authentication-api/authentication-api.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.