---
updatedAt: 2026-08-26T10:35:31.000Z
agentTools:
  projectIndex: https://api-doc.jethr.com/llms.txt
---

# Your first application

How to create your application in Jet HR

# Creating an API Application and Token

This guide walks you through the process of creating an API application and generating your authentication token in Jet HR.

## Prerequisites

Before you begin, ensure you have:

* Admin access to your Jet HR workspace
* Appropriate permissions to manage company settings

<br />

***

<br />

## Step-by-Step Guide

### 1. Access Company Settings

Navigate to **Company Settings** (Impostazioni azienda) from the main sidebar menu.

<Image src="https://files.readme.io/89f952faecd90f8f886ce3ae3108c9e500a4f79f752384dd5c57155144774e5f-api_1.png" align="center" border={true} />

<br />

### 2. Open the API Section

In the left sidebar of Company Settings, locate and click on **API**.

You'll land on the "My Applications" (Le mie applicazioni) page where you can manage all your API applications.

<Image src="https://files.readme.io/fd373aa84a7a7782752ff04236999db8b71262df013e00b48398f5be8f301341-api_2_1.png" align="center" border={true} />

<Callout icon="📘" theme="info">
  **Note:** If this is your first time here, you'll see an empty state with the message "You haven't created any applications yet."
</Callout>

<br />

### 3. Create a New Application

Click the **+ Nuova** (New) button in the top-right corner to start creating your application.

<Image src="https://files.readme.io/481e2e592c2efb0fa56bac25434fa29b15d3f265d5ea1ae11fcb59c01a9c7f51-api_2.png" align="center" border={true} />

A modal dialog will appear with the following fields:

* **Name**: Enter a descriptive name for your application (e.g., "Test application", "Production Integration", "Development Environment")
* **Accessible resources**: Choose between **All** or **Customize**

<Image src="https://files.readme.io/b267e06d6025e4410a4bac3c6e531892ea4c3e0f31fbe7ea4201b88a52072bea-image.png" framed={true} />

<Callout icon="📘" theme="info">
  ### Best practice for application naming

  Use clear, descriptive names that indicate the application's purpose or environment. This makes management easier when you have multiple applications.
</Callout>

<Callout icon="📘" theme="info">
  ### Customize resource access

  If you choose to **Customize** resource access you will have to select, for each one, whether access is read-only or also includes write permissions.

  From an endpoint's reference page, you can see which scope is required for your app to access it.

  ![](https://files.readme.io/2d61e894dc4340a53a57772b75da512235ed239938cf945cf439a7b3afa59399-image.png)
</Callout>

Click **Crea** (Create) to generate your application.

### 4. Save Your API Token

**This is the most critical step.**

After creating your application, a modal will display your newly generated API token.

<Image src="https://files.readme.io/28820afa9b5c6025d9526e56ef7970b03fc73914168be51442bff68ad2a43fe0-api_4.png" align="center" border={true} />

#### ⚠️ **IMPORTANT SECURITY NOTICE**

* **Copy this token immediately** — this is your only opportunity to view it
* **Store it securely** — treat it like a password (use environment variables, secret managers, or secure vaults)
* **Never commit it to version control** — add it to your `.gitignore` or `.env` files
* **You cannot retrieve this token again** — if lost, you'll need to generate a new application

The token format will look like: `T_53PNqKmLCfC_fUnVQB5PpBgplOOn8zzNEaeE0tJVY`

Once you've safely stored your token, click **Ho copiato i codici** (I've copied the codes) to proceed.

<br />

### 5. Verify Your Application

After closing the modal, you'll see your new application listed in the applications table.

<Image src="https://files.readme.io/386da3d7d9dd69aa099a5fde14d8d1fb639f5fc13d9958e55b6a91e1fba5ae41-api_5.png" align="center" border={true} />

The table displays:

* **Nome** (Name): Your application name
* **Chiamate** (Calls): Number of API calls made
* **Creata il** (Created on): Creation date and time
* **Ultimo utilizzo** (Last used): When the token was last used
* **Token**: Masked token (T\_5\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*...)
* **Azioni** (Actions): Options menu with "Vedi dettagli" (View details) and "Elimina" (Delete)

<br />

***

<br />

## Managing Your Applications

### View Application Details

Click the three-dot menu (⋮) next to any application and select **Vedi dettagli** to view:

* Usage statistics
* Request history
* Token information (masked)

### Delete an Application

If you need to revoke access:

1. Click the three-dot menu (⋮)
2. Select **Elimina** (Delete)
3. Confirm the deletion

<Callout icon="⚠️" theme="warn">
  **Warning:** Deleting an application immediately invalidates its token. Any services using this token will lose access instantly.
</Callout>

<br />

***

<br />

## Next Steps

Now that you have your API token, you can:

* Integrate it into your application
* Make authenticated API requests
* Monitor usage in the application dashboard

<br />

***

<br />

## Best Practices

1. **One application per integration** — create separate applications for different services or environments
2. **Rotate tokens regularly** — for enhanced security, periodically create new applications and migrate
3. **Monitor usage** — regularly check the "Chiamate" (Calls) column to detect unusual activity
4. **Document your applications** — keep internal documentation of which application serves which purpose

<br />

***

<br />

## Troubleshooting

**Q: I lost my token, what should I do?**<br />A: Unfortunately, tokens cannot be recovered. You'll need to create a new application and update your integration with the new token.

**Q: Can I regenerate a token for an existing application?**<br />A: No, you need to create a new application to get a new token. Delete the old application once you've migrated to the new one.

**Q: How many applications can I create?**<br />A: There's no specified limit, but keep your applications organized by creating only what you need.

**Need help?** Contact your Jet HR administrator or support team for assistance.