---
title: "Personal Access Tokens"
slug: "personal-access-tokens"
updated: 2025-10-21T08:21:08Z
published: 2025-10-21T08:21:08Z
canonical: "learn.servitly.com/personal-access-tokens"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://learn.servitly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Personal Access Tokens

To allow end-users to access APIs in a secure way without exposing their personal passwords (e.g. encoded in a configuration files), they can use the concept of Personal Access Token (PAT).

A PAT is a long string consisting of numbers, letters, and symbols that can be used as an alternative to a password.

`pat_bd6ed997_bc86_47af_b418_765fb001c477`

A PAT is uniquely associated with the user who creates it, and if needed, can be revoked.

## Managing PATs in the DPS

PAT creation is made directly into the DPS by entering the [*User Profile*](/v1/docs/dps-user-profile#security) page. Within the *Security* tab is the *Personal Access Tokens* section, where you can see the PATs already created and their status.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(281).png)

On a PAT row, by pressing Revoke Token, the token is invalidated, and the PAT is removed. Third-party software using that PAT will no longer be able to make API calls, and a new PAT will have to be created. By pressing the *Add Token* button, it is possible to create a new PAT. A dialog asks the user to provide a name, which is used to identify the created PAT.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(282).png)

By pressing the Save button, the PAT is created, and the dialog offers a way to see and copy the token value.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(283).png)

Note that, once the dialog is closed, there is no way to read the PAT, for security reasons if you lose the token, you have to create a new PAT. PATs belong to a user who creates them, so the user is also responsible to keep them safe.

Note that, the DPS user can manage PATs only if the *WRITE_PAT* permission is assigned to its [user type](/docs/user-types).

For more details about how to use PATs in API requests, refer to this [article](/apidocs/api-main-concepts).