Skip to main content
POST
Delete dashboard

Restrictions

Usage

  • The dashboard is soft-deleted: it disappears from the list but stays in the trash for 30 days and can be restored with POST /rum/dashboard/restore.
  • Deleting an already deleted dashboard returns HTTP 410 DashboardDeleted; a stale expected_revision returns HTTP 409 DashboardRevisionConflict.
  • A dashboard that does not exist returns HTTP 404 DashboardNotFound.
  • The returned revision is the one created by the deletion. Pass it as expected_revision to restore the dashboard.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Delete or restore request. expected_revision must match the current revision.

dashboard_id
string
required

Dashboard ID, a canonical UUIDv7.

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
required

Revision the caller last read. Must be at least 1.

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

Result of moving a dashboard to the trash.