> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-developers/key-concepts/authentication-methods/oauth-access-tokens.md).

# OAuth Access Tokens

OAuth Access Tokens are **short-lived** (they expire in 24 hours) and they are **tied to a specific user's set of permissions**.

CARTO APIs are securitized by [OAuth 2.0](https://auth0.com/docs/authenticate/protocols/oauth), using an OAuth Access Token you'll be able to do operations and call our APIs on behalf of a given user, but you're expected to have a mechanism to renew this allowance.

### How to get an OAuth Access Token

To get an OAuth Access Token, you need to create and use an [OAuth Client](/carto-for-developers/key-concepts/authentication-methods/applications.md)

{% hint style="info" %}
If CARTO hosts your application with **Hosted Apps**, currently in Private Preview, you do not need an OAuth client: CARTO signs the user in and gives your application that user's own OAuth Access Token at runtime. See [Hosted Apps](/carto-for-developers/key-concepts/hosting-your-application.md).
{% endhint %}


---

# 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.carto.com/carto-for-developers/key-concepts/authentication-methods/oauth-access-tokens.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.