---
title: "Create and manage API tokens"
description: "Generate secure credentials to connect external applications with StarNapp and control their permissions and expiration."
url: https://docs.starnapp.com/en/articles/206-create-and-manage-api-tokens
updated: 2026-11-17
language: en
alternates: [es]
---

# Create and manage API tokens

Generate secure credentials to connect external applications with StarNapp and control their permissions and expiration.

> API **tokens** allow another application to identify itself and access certain data or functions of StarNapp without using a person's email and password.

A token works like a **technical password**. Creating it does not automatically connect any application: afterwards we will need to copy it into the program or integration that will communicate with StarNapp.

## **How do we access it?**

We will go to **SETTINGS → CONFIGURATION → API TOKENS**.

![](https://staticfiles.gleap.io/ghelparticle/u4qDwU9eA5ayRf7jZnIzclSTe3q6REoeHvVzcbGqpWfwwEEL3IomB1GdOnuBJfNo7GWu4KGu1DF.png)

On this screen we will see the tokens created for the account and the following information:

-   **Prefix:** allows you to identify the token without displaying its full value.
    
-   **Account:** company or account to which it belongs.
    
-   **Created by:** user who generated it.
    
-   **Expiration:** date until which it can be used.
    
-   **Status:** indicates whether it is active or revoked.
    

> 🔒 Only users with permissions to access the settings can create API tokens for the account.

## **Create an API token**

![](https://staticfiles.gleap.io/ghelparticle/zlztteRBPgxiRNj4P5X3X29IKXc2YGPVq7mgxU4JVPa38FTSQKuVhwec2qF5Z5BGzkVpCxf5msu.png)

1.  We will click **Create API token**.
    
2.  We will choose an **expiration date**.
    
3.  We will select the **role** that the token will use.
    
4.  We will click **Create token**.
    
5.  We will copy the token and save it in a secure location.
    
6.  We will click **Done** to close the window.
    

> ⚠ The complete token is only shown once. When we close the window, we will not be able to view it again.

## **Choose the expiration date**

We can set a duration of:

-   7 days.
    
-   30 days.
    
-   90 days.
    
-   365 days.
    
-   No expiration.
    

We recommend using an expiration date whenever possible. The **No expiration** option should be reserved for permanent integrations that are reviewed periodically.

## **Choose the token role**

The **role** determines what information and functions of StarNapp the application using the token will be able to access.

For example:

-   If a tool only needs to query information to prepare reports, we will use a role with query permissions.
    
-   If an integration must create or update contacts, we will select a role with permissions on Contacts, but without unnecessary access to other areas.
    
-   We will avoid using an administrator role unless the integration really needs all those permissions.
    

> 💡 It is recommended to create a specific role for each integration and grant it only the permissions it needs. Consult [Roles and permissions](gleap://article/67ab3d5c51d051eacc922c0d)_._

We will revoke a token when:

-   The integration is no longer in use.
    
-   We suspect that the token has been shared or exposed.
    
-   We want to replace it with a new one.
    
-   The person or company responsible for the integration stops working with us.
    

To do this, we will locate the token in the list, click the **revoke** option and confirm the action.

Once revoked:

-   Requests made with that token will stop working.
    
-   The token will appear with the status **Revoked**.
    
-   It cannot be reactivated.
    
-   If the integration needs to continue working, we will have to create another token and update it in the external application.
    

## **Security recommendations**

-   Treat the token as if it were a password.
    
-   Store it in a password or secrets manager.
    
-   Do not send it by email or share it in conversations.
    
-   Do not include it in documents, spreadsheets, or code repositories.
    
-   Use a different token for each integration.
    
-   Assign only the necessary permissions.
    
-   Immediately revoke any token that may have been exposed.
    

## **Common issues**

**I cannot see the complete token again**

For security reasons, StarNapp only displays it at the moment of creation. We will need to generate a new one and revoke the previous one if it is no longer going to be used.

**The integration has stopped working**

We will verify that the token has not expired or been revoked. We will also check that it has been completely copied to the external application.

**The integration connects, but cannot perform an action**

We will review the role assigned to the token. It is possible that it does not have permissions to access that section or perform that operation.

**The option to create tokens does not appear**

The user probably does not have the necessary permissions to access this configuration. An administrator should review their role.
