Update an existing dashboard
PUT/perses-public/api/v1/projects/:projectId/dashboards/:dashboardId
Replaces the contents of a dashboard, writing a new version.
Send the complete document you want stored: doc.spec replaces the stored spec in full, so anything you leave out is removed. From doc.metadata, only name and tags are taken; the rest of the stored metadata, including project, is preserved.
The response is the new version: version is incremented and id is a new value, while uid stays the same. createdAt is the creation time of the new version row, not of the original dashboard.
Request
Path Parameters
The id of the folder that contains the dashboard.
The dashboard's uid.
- application/json
Body
required
doc objectrequired
A Perses dashboard document. Only metadata.name is validated by Logz.io; spec is stored as sent and has to be a valid Perses dashboard spec for the dashboard to render in the app.
Possible values: [Dashboard]
metadata objectrequired
The dashboard's identity, and the only field both search endpoints match on. Required on create and update.
Set by the server from the folder in the request path. Any value sent here is replaced.
spec objectrequired
Extra properties are allowed. The Perses dashboard spec. See the Perses dashboard specification for the panel, layout and query plugin shapes.
display object
How the dashboard is labelled in the app.
Default time range, as a duration string.
Auto-refresh interval, as a duration string.
Panel definitions, keyed by panel name.
Grid layouts placing the panels.
Datasources scoped to this dashboard, keyed by name.
Responses
- 200
- 400
- 401
- 404
The updated dashboard, as a new version.
- application/json
- Schema
- Example (from schema)
Schema
The dashboard's stable identifier. It survives updates and moves, and every endpoint addresses a dashboard by this value. This is the one to store.
Identifier of the version row holding the current revision. A new value is issued on every update, and it can't be used to address the dashboard. A dashboard that has never been updated has the same value here as in uid, which makes the two easy to confuse.
Internal marker for the dashboard, equal to uid for dashboards created through this API. The name shown in the app is doc.spec.display.name, and the name that search matches is doc.metadata.name.
The id of the folder holding the dashboard.
doc object
A Perses dashboard document. Only metadata.name is validated by Logz.io; spec is stored as sent and has to be a valid Perses dashboard spec for the dashboard to render in the app.
Possible values: [Dashboard]
metadata objectrequired
The dashboard's identity, and the only field both search endpoints match on. Required on create and update.
Set by the server from the folder in the request path. Any value sent here is replaced.
spec objectrequired
Extra properties are allowed. The Perses dashboard spec. See the Perses dashboard specification for the panel, layout and query plugin shapes.
display object
How the dashboard is labelled in the app.
Default time range, as a duration string.
Auto-refresh interval, as a duration string.
Panel definitions, keyed by panel name.
Grid layouts placing the panels.
Datasources scoped to this dashboard, keyed by name.
Revision number. Starts at 1 and increments on every update.
Numeric id of the principal that created the dashboard. For a dashboard created through this API this is the id of the API token, not of a user.
Numeric id of the principal that last updated the dashboard.
When this version was written. An update stamps a new value, so this is not the creation time of the original dashboard.
Whether the dashboard was made private in the Logz.io app. Privacy can't be changed through this API, and dashboards created through it are never private.
Null unless the dashboard was deleted.
Null unless the dashboard was deleted.
{
"uid": "3fa2c4b1-6d5e-4a90-8b21-7c4e5f6a8b90",
"id": "7d1e5a90-2b44-4c18-9f03-5a6b7c8d9e01",
"name": "3fa2c4b1-6d5e-4a90-8b21-7c4e5f6a8b90",
"projectId": "0b9f6e2a-3c1d-4e8f-9a7b-1c2d3e4f5a6b",
"doc": {
"kind": "Dashboard",
"metadata": {
"name": "cpu-usage",
"project": "string",
"tags": [
"infra"
]
},
"spec": {
"display": {
"name": "CPU usage",
"description": "string"
},
"duration": "1h",
"refreshInterval": "30s",
"variables": [
{}
],
"panels": {},
"layouts": [
{}
],
"datasources": {}
}
},
"version": 2,
"createdBy": 22222,
"updatedBy": 22222,
"createdAt": "2026-08-14T09:12:31.000Z",
"updatedAt": "2026-08-15T10:03:02.000Z",
"isPrivate": false,
"isDeleted": false,
"deletedAt": "2026-09-11T16:54:17.201Z",
"deletedBy": 0
}
The request body has no doc, or the document has no name.
- application/json
- Schema
- Example (from schema)
Schema
Quote this when contacting support about a failed request.
Null for most dashboard errors.
Extra context for the error, when there is any.
{
"statusCode": 400,
"message": "Dashboard name is required",
"requestId": "string",
"errorCode": "string",
"parameters": {}
}
The API token is missing or invalid.
- application/json
- Schema
- Example (from schema)
Schema
Quote this when contacting support about a failed request.
Null for most dashboard errors.
Extra context for the error, when there is any.
{
"statusCode": 400,
"message": "Dashboard name is required",
"requestId": "string",
"errorCode": "string",
"parameters": {}
}
No such dashboard in that folder.
- application/json
- Schema
- Example (from schema)
Schema
Quote this when contacting support about a failed request.
Null for most dashboard errors.
Extra context for the error, when there is any.
{
"statusCode": 400,
"message": "Dashboard name is required",
"requestId": "string",
"errorCode": "string",
"parameters": {}
}