# Headers

A set of HTTP headers must be set when making a request to OCTO API.

These headers can include both standard HTTP headers as well as some custom OCTO API headers. Below are the standard request headers and OCTO custom headers that are required to use:

## Request Headers

<table><thead><tr><th width="222">Header</th><th width="148">Required</th><th>Description</th></tr></thead><tbody><tr><td><code>Authorization</code></td><td>Required</td><td>Your <a href="/pages/TrEUmRteRL7b4GOHvRp6">Authentication</a> <code>Bearer</code> token. </td></tr><tr><td><code>Content-Type</code></td><td>Required</td><td>This must be <code>application/json</code> for all <code>POST</code> <code>PATCH</code> and <code>DELETE</code> requests. </td></tr><tr><td><code>Octo-Capabilities</code></td><td>Required</td><td>A list of the Capabilities (their IDs) to be included in the response. See <a href="/pages/ivh3s8xTKnPPXocbtxHe">Endpoints and Capabilities</a> to learn more about Capabilities. </td></tr></tbody></table>

## Response Headers

<table><thead><tr><th width="224">Header</th><th width="153">Required</th><th>Description</th></tr></thead><tbody><tr><td><code>Content-Type</code></td><td>Required</td><td><code>application/json</code></td></tr><tr><td><code>Octo-Capabilities</code></td><td>Required</td><td>A list of the Capabilities (their IDs) initialized with your request. See <a href="/pages/ivh3s8xTKnPPXocbtxHe">Endpoints and Capabilities</a> to learn more about Capabilities. </td></tr></tbody></table>


---

# Agent Instructions: 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.octo.travel/getting-started/headers.md?ask=<question>
```

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.