> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/connections-and-integrations/api/was-ist-die-authentifizierung-mittels-eines-personal-access-tokens.md).

# What is authentication using a Personal Access Token?

{% hint style="info" %}
**Note:** This feature is available **only available to customers on sipgate classic** available. On sipgate neo, the function is integrated in a different form.
{% endhint %}

You can use personal access tokens for authentication with the sipgate [REST API](https://www.sipgate.io/rest-api) to use. This method is intended to replace the previous basic auth procedure.

Instead of a username and password, authentication with the sipgate REST API uses an individual combination of token ID and token.

**Personal access tokens** offer more security compared to authentication via username and password:

* More **control options** through managing permissions (scopes)
* The token's areas of use can be specified via scopes, so that access is only granted to a restricted area of the account
* If a token has been compromised, it can be deleted
* Username and password do not have to be sent over the network
* Creating a token is secured by **two-factor authentication** if this is enabled

{% hint style="info" %}
**Note:** You can create, manage, and delete your personal access tokens in your [account](https://app.sipgate.com/personal-access-token) account. When assigning permissions (scopes), make sure that you only grant the permissions needed for your application. Unnecessarily granted permissions pose a security risk.
{% endhint %}

Examples of how you can use a personal access token for authentication with the API can be found in our [documentation](https://www.sipgate.io/rest-api/authentication/#personalAccessToken).


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sipgate.de/cloud-telefonanlage/en/connections-and-integrations/api/was-ist-die-authentifizierung-mittels-eines-personal-access-tokens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.