Skip to content

add missing billing api to api keys coverage #7663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shainaraskas wants to merge 3 commits into
base: main
Choose a base branch
from
+2 −1
Open

add missing billing api to api keys coverage #7663

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
acbf1f3
missing billing api from api keys coverage
shainaraskas Jul 30, 2026
4a8474a
fix
shainaraskas Jul 30, 2026
3941aca
Merge branch 'main' into add-billing-api-to-api-key-pages
shainaraskas Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deploy-manage/api-keys.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,5 +31,5 @@ Depending on the APIs you want to use, the API keys to create are different, and
| --- | --- | --- |
| [](api-keys/elasticsearch-api-keys.md) | {applies_to}`stack: ga` | • Use [{{es}}]({{es-apis}}) and [{{kib}}]({{kib-apis}}) APIs in stack-versioned deployments, including ECH, ECE, ECK, and self-managed clusters.<br><br>• Manage remote cluster connections. |
| [](api-keys/serverless-project-api-keys.md) | {applies_to}`serverless: ga`| Use [{{es}} {{serverless-short}}]({{es-serverless-apis}}) and [{{kib}} {{serverless-short}}]({{kib-serverless-apis}}) APIs. |
| [](api-keys/elastic-cloud-api-keys.md) | {applies_to}`ess: ga` {applies_to}`serverless: ga` | • Manage your {{ecloud}} organization, {{ech}} deployments, and {{serverless-short}} projects using the [{{ecloud}}]({{cloud-apis}}) and [{{ecloud}} {{serverless-short}}]({{cloud-serverless-apis}}) APIs.<br><br>• {applies_to}`serverless: ga` Use [{{es}} {{serverless-short}}]({{es-serverless-apis}}) and [{{kib}} {{serverless-short}}]({{kib-serverless-apis}}) APIs. Using {{ecloud}} keys for project-level API access allows you to create keys that can interact with multiple projects, and manage API access centrally from the {{ecloud}} console. |
| [](api-keys/elastic-cloud-api-keys.md) | {applies_to}`ess: ga` {applies_to}`serverless: ga` | • Manage your {{ecloud}} organization, {{ech}} deployments, and {{serverless-short}} projects using the [{{ecloud}}]({{cloud-apis}}) and [{{ecloud}} {{serverless-short}}]({{cloud-serverless-apis}}).<br><br>• Manage billing for your organizations using the [{{ecloud}} Billing]({{cloud-billing-apis}}) APIs.<br><br>• {applies_to}`serverless: ga` Use [{{es}} {{serverless-short}}]({{es-serverless-apis}}) and [{{kib}} {{serverless-short}}]({{kib-serverless-apis}}) APIs. Using {{ecloud}} keys for project-level API access allows you to create keys that can interact with multiple projects, and manage API access centrally from the {{ecloud}} console. |
|[](api-keys/elastic-cloud-enterprise-api-keys.md) | {applies_to}`ece: ga` | Manage your {{ece}} platform and deployments using the [{{ece}}]({{ece-apis}}) API. |
1 change: 1 addition & 0 deletions deploy-manage/api-keys/elastic-cloud-api-keys.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ products:

* [{{ecloud}}]({{cloud-apis}}) APIs
* [{{ecloud}} {{serverless-short}}]({{cloud-serverless-apis}}) APIs
* [{{ecloud}} Billing]({{cloud-billing-apis}}) APIs
* {applies_to}`serverless: ga` Optionally, [{{es}} {{serverless-full}}]({{es-serverless-apis}}) and [{{kib}} {{serverless-full}}]({{kib-serverless-apis}}) APIs

Only **Organization owners** can create and manage API keys. An API key is not tied to the user who created it. When creating a key, you assign it specific roles to control its access to organizational resources, including hosted deployments and serverless projects. If a user leaves the organization, the API keys they have created will still function until they expire.
Expand Down
Loading