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

# Authentication

The Duro GraphQL API uses Bearer token and API key (via `x-api-key` header) authentication. All API requests must include an authorization token in the header.

### Obtaining an API Authentication Token

To get started with the Duro API, you'll need to:

1. Create a Duro account at [durohub.com](https://durohub.com)
2. Navigate to your account settings
3. Generate an API token from the Developer section
4. Your URL to get an API key is: `https://durohub.com/org/@<your org slug>/libs/<your library slug>/settings/api-keys`

![API Key Created Window](/files/ToqWcFiFQ4l30WbBRvrI)

### Using the Token

Include your API token in all requests using the `x-api-key` header:

```graphql
x-api-key: YOUR_API_TOKEN
```

### Token Security

* Never share your API tokens
* Rotate tokens regularly
* Use different tokens for development and production
* Store tokens securely in environment variables

{% hint style="warning" %}
Never commit API tokens to version control or expose them in client-side code.
{% endhint %}

### Next Steps

Learn how to make your first API call in the [Hello World](/getting-started/hello-world.md) guide.


---

# 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.durohub.com/getting-started/authentication.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.