# 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="authentication">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="endpoints-and-capabilities">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="endpoints-and-capabilities">Endpoints and Capabilities</a> to learn more about Capabilities. </td></tr></tbody></table>