# API Keys

This section displays a table listing all API keys configured for your organization.

For each key, the table displays the following information:

* Title
* Unique identifier (ID)
* User who created the key
* Creation date
* Expiration date

A contextual menu <img src="/files/2puUUOGnaw4P3GWbyxsG" alt="" data-size="line"> in each column header allows you to sort, filter, hide, or display attributes according to your needs.

## Adding an API Key

1. Click **Add Key**.
2. Enter a name and expiration date, then choose the role assigned to the key (only Manager and User roles are available). Fields marked with an asterisk (\*) are required.
3. Click **Create**.

{% hint style="info" %}
A message reminds you that this is a private key and that it will no longer be accessible after the window is closed. Make sure to copy it immediately using the copy icon <img src="/files/yIxiicUdUF5cEXf7Nnu7" alt="" data-size="line"> if you need to use it elsewhere.&#x20;
{% endhint %}

Click **OK** to complete the creation. The key is then added to the table.&#x20;

## Managing API Keys

To manage an API key, hover over its row to display the contextual menu, then click it to access the available options:

* **Display information**
* **Delete**

The information view displays:

* Title
* Creator
* Role
* Email address
* Expiration date

You can copy the email address using the copy icon <img src="/files/JcwmDZ7PE2yTvf2NxO2y" alt="" data-size="line">.

## Deleting an API Key

You can delete API keys that are no longer needed. However, be aware of the implications: a key may own resources such as data sources, projects, layers, or tables.

Before deleting a key, make sure to transfer ownership of its resources to another member of the organization. Otherwise, the resources will be deleted along with the key.

#### Deletion steps

1. Click the contextual menu icon, then click **Delete**.
2. Confirm your intention in the dialog box that appears.
3. If the key owns resources, a list of members with the Manager role will be displayed. Select the member to whom the resources will be transferred.
4. If the key owns no resources, confirm the deletion.

The selected member becomes the owner of all transferred resources. Access permissions (ACL) associated with the deleted key are removed.

{% hint style="warning" %}
Resources without another owner will be permanently deleted.
{% endhint %}

{% hint style="warning" %}
Deleting an API key is irreversible. The key is permanently removed from JMap Cloud.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/managing-the-organization/api-keys.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.