> 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/public.md).

# Public

### **Description**

The "public connection type is generally used for open and unauthenticated API connections where the only required configuration information is the endpoint URL.

However, since this type also supports the ability to add additional custom HTTP headers, you can also use it to configure connections that don't have their own type in the list of connection types.

### **Required Information**

* **API Endpoint:** The URL of the API endpoint.

### **Optional Information**

* **Headers:** A list of key/value pairs for populating HTTP headers for each request to the API endpoint. Click "+" to add a new header and enter the key and value.

### Example

An example of using the "Public" connection type for an otherwise unsupported connection is for the "ApiKey" connection type, which is very similar to the "Bearer Token" connection type. Since this type isn't yet supported, you can configure a custom header on the connection as follows:

Key: Authorization\
Value: ApiKey \<token>


---

# 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/public.md?ask=<question>&goal=<user_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.