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

# Bearer

## Bearer Connection

### **Description**

The "Bearer" connection type supports HTTP Bearer Authentication. This method requires that a bearer token be provided in the HTTP authentication header.

### **Required Information**

Once you have selected the "bearer" type, the system will prompt for the following fields:

* **API Endpoint:** The URL of the API to use.
* **Bearer Token:** The token used for authentication.
* **HTTP Headers:** Additional HTTP headers can also be added if required by clicking on the "+" next to "HEADERS" and adding a key/value pair for each header to be added.

### **Example Header**

```http
Authorization: Bearer your_token_here
```

### **Usage**

This connection type is commonly used when you have an OAuth 2.0 token or similar token-based authentication system.


---

# 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.contextual.io/documentation-and-resources/components-and-data/connections/types-of-connections/bearer.md?ask=<question>&goal=<endgoal>
```

`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.
