Jack Baldry
4cacab01f4
* Use relative aliases for all non-current Grafana aliases Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Remove all current page aliases find docs/sources -type f -name '*.md' -exec sed -z -i 's#\n *- /docs/grafana/latest/[^\n]*\n#\n#' {} \; find docs/sources -type f -name '*.md' -exec sed -Ez -i 's#\n((aliases:\n *-)|aliases:\n)#\n\2#' {} \; Signed-off-by: Jack Baldry <jack.baldry@grafana.com> Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
13 lines
574 B
Markdown
13 lines
574 B
Markdown
---
|
|
description: Learn about using API keys in Grafana
|
|
menuTitle: About API keys
|
|
title: About API keys in Grafana
|
|
weight: 30
|
|
---
|
|
|
|
# About API keys in Grafana
|
|
|
|
An API key is a randomly generated string that external systems use to interact with Grafana HTTP APIs.
|
|
|
|
When you create an API key, you specify a **Role** that determines the permissions associated with the API key. Role permissions control that actions the API key can perform on Grafana resources. For more information about creating API keys, refer to [Create an API key]({{< relref "./create-api-key.md#">}}).
|