# Authentication

{% hint style="success" %}
To access the Dashdoc API, you must authenticate each request using an API token. This token should be included in the HTTP header of your requests.
{% endhint %}

### How to Include the API Token

For all API requests, the API token must be provided in the `Authorization` header. The format for the header is as follows:

```http
Authorization: Token YOUR_API_TOKEN
```

### Example Using cURL

{% code title="Example of curl authenticated request :" %}

```bash
curl -X GET -H "Authorization: Token 5a4d02fad3975c169e9f538d8e733ead4069703x" "https://www.dashdoc.eu/api/v4/transports/"
```

{% endcode %}

### Example Using Postman

<figure><img src="/files/oPI0fEkywdA88dVdJSUY" alt=""><figcaption></figcaption></figure>

### How to generate an API token ?

You can obtain the API token from the Dashdoc web app:

{% content-ref url="/pages/Nr1pz0NrQtuhEBO7vEAb" %}
[Get the API token](/docs/integrate-your-software/setup/get-the-api-token.md)
{% endcontent-ref %}

{% hint style="warning" %}
Keep in mind that an API token is **tied to a specific company**, giving access to all company's data. You can only have one active API token at any time.
{% endhint %}


---

# 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://developer.dashdoc.com/docs/get-started/core-api-concepts/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.