> 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/es/api-publica-de-exoclick/token-de-api-vs-token-bearer.md).

# Token de API vs token Bearer

Al trabajar con la API de ExoClick, encontrarás dos tipos de tokens de autenticación: tokens de API y tokens Bearer. Comprender la diferencia entre ellos es fundamental para usar la API de forma segura y eficaz.

Esta es la diferencia:

## Token de API

* Es permanente, hasta que lo desactives o elimines.
* Se usa para autenticar tu cuenta en la API cuando inicias sesión.
* Se crea en [Mi perfil > Tokens de API](https://docs.exoclick.com/exoclick-docs/my-profile#api-tokens-tab).
* Se muestra completo una sola vez, al crearlo. Guárdalo en un lugar seguro.

## Token Bearer

* Es temporal y vence al cabo de poco tiempo.
* Se emite cuando inicias sesión con tu token de API.
* Se envía con cada solicitud que requiere autenticación, para que no tengas que enviar tu token de API cada vez.
* Aporta más seguridad, ya que solo es válido durante un tiempo limitado.

**En resumen:** Tu token de API identifica quién eres. El token Bearer es una clave temporal que te permite enviar solicitudes de forma segura.


---

# 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/es/api-publica-de-exoclick/token-de-api-vs-token-bearer.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.
