---
title: Serverless project API keys
description: In Serverless projects, the following types of API keys exist: Personal API keys, that you can create to allow external services to access your serverless...
url: https://www.elastic.co/elastic/docs-builder/docs/4572/deploy-manage/api-keys/serverless-project-api-keys
products:
- Elastic Cloud Serverless
- Elastic Documentation
applies_to:
- Elastic Cloud Serverless: Generally available
---
# Serverless project API keys
In Serverless projects, the following types of API keys exist:
- **Personal** API keys, that you can create to allow external services to access your serverless project, including the [Elasticsearch](https://www.elastic.co/docs/api/doc/elasticsearch/) and [Kibana](https://www.elastic.co/docs/api/doc/kibana/) APIs, on behalf of a user.
- **Managed** API keys, created and managed by Kibana to correctly run background tasks.
As an alternative to using Serverless project API keys, which are tied to a single project, you can create [Elastic Cloud API keys](https://www.elastic.co/elastic/docs-builder/docs/4572/deploy-manage/api-keys/elastic-cloud-api-keys) that include access to projects' Elasticsearch and Kibana APIs. This allows you to create keys that can interact with multiple projects, and manage API access centrally from the Elastic Cloud console.The [cross-project search feature](/elastic/docs-builder/docs/4572/deploy-manage/cross-project-search-config/cps-config-access-and-scope#manage-user-and-api-key-access) requires Elastic Cloud API keys for programmatic access.
To manage API keys in Kibana, go to the **API keys** management page in the navigation menu or use the [global search field](https://www.elastic.co/elastic/docs-builder/docs/4572/explore-analyze/find-and-organize/find-apps-and-objects).
## Create an API key
The following options are available to create an API key:
- As a quick option, [use the simple API key creation menu](#simple-api-key-creation).
- For more complex key creation needs, [use the API key page](#advanced-api-key-creation).
- Create an API key [using the Elasticsearch API](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-security-create-api-key).
### Simple API key creation
You can create a basic personal API key from anywhere in Kibana:
1. From the **Help menu** `question`, select **Connection details → API key**.
2. Give the key a name.
3. Select **Create API key**.
Your personal API key is created with a default expiration of 90 days from the time of creation. You can manage the key from the **API keys** page.
### Advanced API key creation
Use the API key page to create a personal API key with configurable options.
1. Go to the **API keys** management page in the navigation menu or use the [global search field](https://www.elastic.co/elastic/docs-builder/docs/4572/explore-analyze/find-and-organize/find-apps-and-objects).
2. Select **Create API key**.
3. Give the key a name.
4. Optionally, set an expiry date. By default the API key does not expire, but it's a good security practice to give the key a limited lifespan.
5. Optionally, configure access to specific Elasticsearch APIs and resources by assigning the key with predefined roles or custom privileges. Refer to [Control security privileges](#api-keys-restrict-privileges) and the [Create API key](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-security-create-api-key) API documentation to learn more.
6. Add any additional metadata about the API key as one or more key-value pairs. Refer to the [Create API key](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-security-create-api-key) API documentation for examples.
Once created, you can copy the encoded API key and use it to send requests to the Elasticsearch HTTP API. For example:
```bash
curl "${ES_URL}" \
-H "Authorization: ApiKey ${API_KEY}"
```
API keys are intended for programmatic access. Don’t use API keys to authenticate access using a web browser.
### Control security privileges
When you create or update an API key, use **Control security privileges** to configure access to specific Elasticsearch APIs and resources. Define the permissions using a JSON `role_descriptors` object, where you specify one or more roles and the associated privileges.
For example, the following `role_descriptors` object defines a `books-read-only` role that limits the API key to `read` privileges on the `books` index.
```json
{
"books-read-only": {
"cluster": [],
"indices": [
{
"names": ["books"],
"privileges": ["read"]
}
],
"applications": [],
"run_as": [],
"metadata": {},
"transient_metadata": {
"enabled": true
}
}
}
```
For the `role_descriptors` object schema, check out the [`/_security/api_key` endpoint](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-security-create-api-key) docs. For supported privileges, check [Security privileges](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/4572/reference/elasticsearch/security-privileges#privileges-list-indices).
## Update an API key
In **API keys**, click on the name of the key. You can update only **Control security privileges** and **Include metadata**.
## View and delete API keys
The **API keys** app lists your API keys, including the name, date created, and status. When API keys expire, the status changes from `Active` to `Expired`.
You can delete API keys individually or in bulk.
## Related pages
- [Find your Serverless project connection details](https://www.elastic.co/elastic/docs-builder/docs/4572/deploy-manage/deploy/elastic-cloud/find-connection-details-serverless): Pair a key with your project's Elasticsearch endpoint to connect clients and tools.