> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/api/screendesk-api/authentication.md).
# Authentication
The Screendesk API uses Personal access tokens to authenticate requests.
{% hint style="info" %}
Access tokens are tied to the Screendesk user account for which they were created. A token provides the same level of access & privileges that its associated Screendesk user account would have.
{% endhint %}
### Create an access token
To create an access token, sign in to your Screendesk account and go to the "Personal Settings" page. In the “[API Tokens](https://app.screendesk.io/profile/api)” tab click the “Create an API Token” button.
Enter a token name and click on the “Create token” button. Once the token gets created, you will be able to copy the token to your clipboard.
You should now see the new token information in the table. You are able to view the raw token anytime you need to, as well as edit the token name and revoke the token.
### How to use your access token
Once you have created your access token, you can use it to make requests to the API. Requests are authenticated using [HTTP Bearer Authentication](https://tools.ietf.org/html/rfc6750). You must provide the access token in the Authorization header:
```
Authorization: Bearer {ACCESS_TOKEN}
```
---
# 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.screendesk.io/api/screendesk-api/authentication.md?ask=&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.
