> For the complete documentation index, see [llms.txt](https://docs.octo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.octo.travel/getting-started/authentication.md).

# Authentication

OCTO uses Bearer authentication. To authenticate requests, an API key must be sent as a Bearer token in the Authorization [header](/getting-started/headers.md) of your request:

```http
GET /supplier HTTP/1.1
Host: {host}
Authorization: Bearer {your_API_key}
```

{% hint style="info" %}
For security reasons, it's recommended to use a single unique API key per reseller-supplier relationship.&#x20;
{% endhint %}

All API requests must be made over HTTPS. Calls made over plain HTTP should fail. API requests without authentication will also fail. If the token is invalid or is deactivated by Supplier a 403 Forbidden error should be returned.


---

# 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:

```
GET https://docs.octo.travel/getting-started/authentication.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.
