> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/api/exoclick-public-api/api-token-vs-bearer-token.md).

# API Token vs Bearer Token

When working with the ExoClick API, you'll encounter two types of authentication tokens: API tokens and Bearer tokens. Understanding the difference between them is crucial for secure and effective API usage.

Here's the distinction:

## API Token

* Permanent, until you disable or delete it.
* Used to authenticate your account with the API when you log in.
* Created in [My Profile > API Tokens](https://docs.exoclick.com/exoclick-docs/my-profile#api-tokens-tab).
* Shown in full only once, when you create it. Store it somewhere safe.

## Bearer Token

* Temporary, and expires after a short time.
* Issued when you log in with your API token.
* Sent with every request that requires authentication, so your API token isn't sent each time.
* Adds security, as it's only valid for a limited time.

**In short:** Your API token identifies who you are. The bearer token is a temporary key that lets you make requests safely.


---

# 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.exoclick.com/api/exoclick-public-api/api-token-vs-bearer-token.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.
