> 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?

Learn how to create and manage Personal Access Tokens for secure authentication with the sipgate REST API.

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

Instead of a username and password, a unique combination of token ID and token is used for authentication with the sipgate REST API.

**Personal Access Token** offer more security than authentication with username and password:

* More **control options** by managing permissions (scopes)
* The areas of use for the tokens can be specified via the scopes, so that access is granted only to a limited 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
* The creation of a token is secured by the **two-factor authentication** if it 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) create, manage and delete. When assigning permissions (scopes), make sure that you only grant the permissions required 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
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=<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.