This is documentation for the next version of Grafana. For the latest stable release, go to the latest version.
New Dashboard APIs
If you are running Grafana Enterprise, for some endpoints you’ll need to have specific permissions. Refer to Role-based access control permissions for more information.
To view more about the new api structure, refer to API overview.
Create Dashboard
POST /apis/dashboard.grafana.app/v1beta1/namespaces/:namespace/dashboards
Creates a new dashboard.
- namespace: to read more about the namespace to use, see the API overview.
Required permissions
See note in the introduction for an explanation.
Example Create Request:
JSON Body schema:
- metadata.name – The Grafana unique identifier. If you do not want to provide this, set metadata.generateName instead to the prefix you would like for the randomly generated uid (cannot be an empty string).
- metadata.annotations.grafana.app/folder - Optional field, the unique identifier of the folder under which the dashboard should be created.
- spec – The dashboard json.
Example Response:
Status Codes:
- 201 – Created
- 400 – Errors (invalid json, missing or invalid fields, etc)
- 401 – Unauthorized
- 403 – Access denied
- 409 – Conflict (dashboard with the same uid already exists)
Update Dashboard
PUT /apis/dashboard.grafana.app/v1beta1/namespaces/:namespace/dashboards/:uid
Updates an existing dashboard via the dashboard uid.
- namespace: to read more about the namespace to use, see the API overview.
- uid: the unique identifier of the dashboard to update. this will be the name in the dashboard response
Required permissions
See note in the introduction for an explanation.
Example Update Request:
POST /apis/dashboard.grafana.app/v1beta1/namespaces/default/dashboards/gdxccn HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
{
"metadata": {
"name": "gdxccn",
"annotations": {
"grafana.app/folder": "fef30w4jaxla8b",
"grafana.app/message": "commit message"
},
},
"spec": {
"title": "New dashboard - updated",
"schemaVersion": 41,
...
}
}
JSON Body schema:
- metadata.name – The unique identifier.
- metadata.annotations.grafana.app/folder - Optional field, the unique identifier of the folder under which the dashboard should be created.
- metadata.annotations.grafana.app/message - Optional field, to set a commit message for the version history.
- spec – The dashboard json.
Example Response:
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 485
{
"kind": "Dashboard",
"apiVersion": "dashboard.grafana.app/v1beta1",
"metadata": {
"name": "gdxccn",
"namespace": "default",
"uid": "Cc7fA5ffHY94NnHZyMxXvFlpFtOmkK3qkBcVZPKSPXcX",
"resourceVersion": "2",
"generation": 2,
"creationTimestamp": "2025-03-06T19:57:18Z",
"annotations": {
"grafana.app/folder": "fef30w4jaxla8b",
"grafana.app/createdBy": "service-account:cef2t2rfm73lsb",
"grafana.app/updatedBy": "service-account:cef2t2rfm73lsb",
"grafana.app/updatedTimestamp": "2025-03-07T02:58:36Z"
}
},
"spec": {
"schemaVersion": 41,
"title": "New dashboard - updated",
...
}
}
Status Codes:
- 200 – OK
- 400 – Errors (invalid json, missing or invalid fields, etc)
- 401 – Unauthorized
- 403 – Access denied
- 409 – Conflict (dashboard with the same version already exists)
Get Dashboard
GET /apis/dashboard.grafana.app/v1beta1/namespaces/:namespace/dashboards/:uid
Gets a dashboard via the dashboard uid.
- namespace: to read more about the namespace to use, see the API overview.
- uid: the unique identifier of the dashboard to update. this will be the name in the dashboard response
Note: For large dashboards, add /dto
to the end of the URL to get the full dashboard body.
Required permissions
See note in the introduction for an explanation.
Example Get Request:
GET /apis/dashboard.grafana.app/v1beta1/namespaces/default/dashboards/gdxccn HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 485
{
"kind": "Dashboard",
"apiVersion": "dashboard.grafana.app/v1beta1",
"metadata": {
"name": "gdxccn",
"namespace": "default",
"uid": "Cc7fA5ffHY94NnHZyMxXvFlpFtOmkK3qkBcVZPKSPXcX",
"resourceVersion": "2",
"generation": 2,
"creationTimestamp": "2025-03-06T19:57:18Z",
"annotations": {
"grafana.app/createdBy": "service-account:cef2t2rfm73lsb",
"grafana.app/updatedBy": "service-account:cef2t2rfm73lsb",
"grafana.app/updatedTimestamp": "2025-03-07T02:58:36Z"
}
},
"spec": {
"schemaVersion": 41,
"title": "New dashboard - updated",
...
}
}
Status Codes:
- 200 – OK
- 401 – Unauthorized
- 403 – Access denied
- 404 – Not Found
List Dashboards
GET /apis/dashboard.grafana.app/v1beta1/namespaces/:namespace/dashboards
Lists all dashboards in the given organization. You can control the maximum number of dashboards returned through the limit
query parameter. You can then use the continue
token returned to fetch the next page of dashboards.
- namespace: to read more about the namespace to use, see the API overview.
Note: to read more about the namespace to use, see the API overview.
Required permissions
See note in the introduction for an explanation.
Example Get Request:
GET /apis/dashboard.grafana.app/v1beta1/namespaces/default/dashboards?limit=1 HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
Status Codes:
- 200 – OK
- 401 – Unauthorized
- 403 – Access denied
Delete Dashboard
DELETE /apis/dashboard.grafana.app/v1beta1/namespaces/:namespace/dashboards/:uid
Deletes a dashboard via the dashboard uid.
- namespace: to read more about the namespace to use, see the API overview.
- uid: the unique identifier of the dashboard to update. this will be the name in the dashboard response
Required permissions
See note in the introduction for an explanation.
Example Delete Request:
DELETE /apis/dashboard.grafana.app/v1beta1/namespaces/default/dashboards/gdxccn HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 78
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"details": {
"name": "gdxccn",
"group": "dashboard.grafana.app",
"kind": "dashboards",
"uid": "Cc7fA5ffHY94NnHZyMxXvFlpFtOmkK3qkBcVZPKSPXcX"
}
}
Status Codes:
- 200 – OK
- 401 – Unauthorized
- 403 – Access denied
- 404 – Not found
Gets the home dashboard
GET /api/dashboards/home
Will return the home dashboard.
Example Request:
GET /api/dashboards/home HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
Tags for Dashboard
GET /api/dashboards/tags
Get all tags of dashboards
Example Request:
GET /api/dashboards/tags HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
HTTP/1.1 200
Content-Type: application/json
[
{
"term":"tag1",
"count":1
},
{
"term":"tag2",
"count":4
}
]
Dashboard Search
See Folder/Dashboard Search API.
APIs
Unique identifier (uid) vs identifier (id)
The unique identifier (uid) of a dashboard can be used to uniquely identify a dashboard within a given org. It’s automatically generated if not provided when creating a dashboard. The uid allows having consistent URLs for accessing dashboards and when syncing dashboards between multiple Grafana installs, see dashboard provisioning for more information. This means that changing the title of a dashboard will not break any bookmarked links to that dashboard.
The uid can have a maximum length of 40 characters.
The identifier (id) of a dashboard is deprecated in favor of the unique identifier (uid).
Create / Update dashboard
POST /api/dashboards/db
Creates a new dashboard or updates an existing dashboard. When updating existing dashboards, if you do not define the folderId
or the folderUid
property, then the dashboard(s) are moved to the root level. (You need to define only one property, not both).
Note: This endpoint is not intended for creating folders, use
POST /api/folders
for that.
Required permissions
See note in the introduction for an explanation.
Example Request for new dashboard:
POST /api/dashboards/db HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
{
"dashboard": {
"id": null,
"uid": null,
"title": "Production Overview",
"tags": [ "templated" ],
"timezone": "browser",
"schemaVersion": 16,
"refresh": "25s"
},
"folderUid": "l3KqBxCMz",
"message": "Made changes to xyz",
"overwrite": false
}
JSON Body schema:
- dashboard – The complete dashboard model.
- dashboard.id – id = null to create a new dashboard.
- dashboard.uid – Optional unique identifier when creating a dashboard. uid = null will generate a new uid.
- dashboard.refresh - Set the dashboard refresh interval. If this is lower than the minimum refresh interval, then Grafana will ignore it and will enforce the minimum refresh interval.
- folderId – The id of the folder to save the dashboard in.
- folderUid – The UID of the folder to save the dashboard in. Overrides the
folderId
. - overwrite – Set to true if you want to overwrite an existing dashboard with a given dashboard UID.
- message - Set a commit message for the version history.
Example Request for updating a dashboard:
POST /api/dashboards/db HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
{
"dashboard": {
"id": 1,
"title": "Production Overview Updated",
"tags": [ "templated" ],
"timezone": "browser",
"schemaVersion": 16,
"version": 1,
"refresh": "25s"
},
"folderUid": "l3KqBxCMz",
"message": "Made changes to xyz",
"overwrite": false
}
Example Response:
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 78
{
"id": 1,
"uid": "e883f11b-77c0-4ee3-9a70-3ba223d66e56",
"url": "/d/e883f11b-77c0-4ee3-9a70-3ba223d66e56/production-overview-updated",
"status": "success",
"version": 2
"slug": "production-overview-updated",
}
Status Codes:
- 200 – Created
- 400 – Errors (invalid json, missing or invalid fields, etc)
- 401 – Unauthorized
- 403 – Access denied
- 412 – Precondition failed
The 412 status code is used for explaining that you cannot create the dashboard and why. There can be different reasons for this:
- The dashboard has been changed by someone else,
status=version-mismatch
- A dashboard with the same uid already exists,
status=name-exists
- The dashboard belongs to plugin
<plugin title>
,status=plugin-dashboard
The response body will have the following properties:
HTTP/1.1 412 Precondition Failed
Content-Type: application/json; charset=UTF-8
Content-Length: 97
{
"message": "The dashboard has been changed by someone else",
"status": "version-mismatch"
}
Get dashboard by uid
GET /api/dashboards/uid/:uid
Will return the dashboard given the dashboard unique identifier (uid). Information about the unique identifier of a folder containing the requested dashboard might be found in the metadata.
Required permissions
See note in the introduction for an explanation.
Example Request:
GET /api/dashboards/uid/cIBgcSjkk HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
HTTP/1.1 200
Content-Type: application/json
{
"dashboard": {
"id": 1,
"uid": "cIBgcSjkk",
"title": "Production Overview",
"tags": [ "templated" ],
"timezone": "browser",
"schemaVersion": 16,
"version": 0
},
"meta": {
"isStarred": false,
"url": "/d/cIBgcSjkk/production-overview",
"folderId": 2,
"folderUid": "l3KqBxCMz",
"slug": "production-overview" //deprecated in Grafana v5.0
}
}
Status Codes:
- 200 – Found
- 401 – Unauthorized
- 403 – Access denied
- 404 – Not found
Delete dashboard by uid
DELETE /api/dashboards/uid/:uid
Will delete the dashboard given the specified unique identifier (uid).
Required permissions
See note in the introduction for an explanation.
Example Request:
DELETE /api/dashboards/uid/cIBgcSjkk HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
HTTP/1.1 200
Content-Type: application/json
{
"title": "Production Overview",
"message": "Dashboard Production Overview deleted",
"id": 2
}
Status Codes:
- 200 – Deleted
- 401 – Unauthorized
- 403 – Access denied
- 404 – Not found
Gets the home dashboard
GET /api/dashboards/home
Will return the home dashboard.
Example Request:
GET /api/dashboards/home HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
Tags for Dashboard
GET /api/dashboards/tags
Get all tags of dashboards
Example Request:
GET /api/dashboards/tags HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
Example Response:
HTTP/1.1 200
Content-Type: application/json
[
{
"term":"tag1",
"count":1
},
{
"term":"tag2",
"count":4
}
]