API Keys

This section displays a table listing all API keys associated with your organization.

For each key, the table shows the following information:

• Title

• Unique identifier (ID)

• Name of the user who created it

• Creation date

• Expiration date

A context menu in each column header allows you to sort, filter, hide, or show specific attributes as needed.

Adding an API key

To add a new API key:

1. Click Create new API key.

2. Enter a name, select an expiration date, and choose a role from the dropdown menu (only Editor and Viewer roles can be assigned to API keys). Fields marked with an asterisk (*) are required.

3. Click Create.

A message will inform you that the key is private and must be kept secret and secure. Once the window is closed, the key cannot be viewed again. Be sure to copy it immediately using the icon if you need it for future use.

Click OK to confirm. The key will now appear in the table.

Managing API keys

To manage an existing API key hover over the row of the key to reveal the menu, then click it to access the following options:

• View information

• Delete

The information view displays:

• The title

• The creator’s name

• The assigned role

• The email address

• The expiration date

You can copy the email address to the clipboard using the icon.

Delete an API key

You may delete unused API keys, but be aware of the consequences: a key may own resources such as data sources, projects, layers, and tables.

Before deletion, you should transfer ownership of these resources to another organization member. Otherwise, they will be permanently deleted along with the key.

Deletion steps:

1. Click the menu next to the key, then select Delete.

2. A confirmation message will appear. Confirm your intention to proceed.

3. If the key owns resources, a list of members with the Editor role will be displayed. Select one to transfer resource ownership.

4. If the key does not own any resources, you’ll be asked to confirm the final deletion.

The selected member becomes the new owner of the transferred resources. The key’s access permissions (ACL entries) are removed.

Any resources exclusively owned by the deleted key will also be permanently deleted. Deleting an API key is irreversible—it is permanently removed from JMap Cloud.