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

# Authenticating requests

The REST API uses a single bearer token for everything: accounts, transfers and agent wallets. Every request must carry an API key, and keys are issued from a Glade account.

***

## Generate a key

Keys come from the **Developer** area of the dashboard.

1. Sign in to Glade.
2. Go to **Dashboard → Developer → API Keys**.
3. Select **Generate New Key**.
4. Label it so you can tell keys apart later. Something like `production`, `dev` or `internal-tool` works well.
5. Copy it somewhere safe immediately. The key is shown only this one time.

A key belongs to the account that generated it. Transfers sent with it are just as confidential as transfers sent from the app, so automating a payment does not cost you any privacy.

***

## Send the key with each request

Put the key in the `Authorization` header:


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.useglade.org/api-reference/authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.