> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/components-and-data/connections/types-of-connections/basic.md). # Basic ## Basic Connection ### **Description** The "Basic" connection type supports HTTP Basic Authentication. This method requires that a username and password are sent in the HTTP authentication header. ### **Required Information** Once the "basic" type has been selected from the drop-down menu, the system will prompt for the following information: * **Endpoint:** The URL of the API endpoint * **Username**: The username for authentication. * **Password**: The password for authentication. ### **Example Header** An example Basic Authentication header is shown below. However the developer does not need to do anything other than create the connection and the system will handle the creation of the header automatically, including the encoding of the username:password in Base64. ```http Authorization: Basic base64(username:password) ``` ### **Usage** This connection type is typically used when simple username and password credentials are sufficient for authentication. --- # 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.contextual.io/documentation-and-resources/components-and-data/connections/types-of-connections/basic.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.