> 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.md). # Connections Connections are Contextual's way of making integration with third-party APIs and services much easier than they otherwise would be. When making API calls from a Flow, Connections provide a number of important capabilities: * Connections insulate the developer from needing to provide the URL of the external service. * They also encapsulate the authentication strategy for the particular service (e.g. Basic Auth, OAUTH2 Client Grant, etc) and ensure that the developer doesn't have to be aware of things like token exchanges/renewals. * They store any secrets associated with the connection in an encrypted key vault, ensuring that such secrets, bearer tokens, or passwords are not accessible to anyone other than administrators with access to the connections. These features ensure that flow developers have full access to third-party APIs but no access or responsibility to the API configurations and credentials. --- # 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.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.