Skip to main content
POST
Restore dashboard

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Restore a trashed dashboard, optionally into a different folder.

dashboard_id
string
required

Canonical UUIDv7 of the dashboard.

Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-7[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$
expected_revision
integer<uint64>
required

Revision the caller last read. The write fails with DashboardRevisionConflict unless it still matches the stored revision.

Required range: x >= 1
folder_id
integer<uint64> | null

Destination folder. Omit to restore to the original folder; when the original folder is no longer writable the call fails with RestoreFolderRequired and you must pass one.

Required range: x >= 1

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

A stored dashboard: its identity, revision counter, placement and full definition. revision increments on every accepted write and must be echoed back as expected_revision for the next mutation.