Skip to main content
POST
Get dashboard revision

Restrictions

Usage

  • Revision numbers are per dashboard and start at 1 (the create). Revisions older than the latest 20 are pruned and return DashboardNotFound (HTTP 404).
  • Reading is open to every member of the account, so dashboards in every folder are visible whichever team the folder belongs to; reading is open to every member of the account, whichever team the folder belongs to; a dashboard in the trash returns DashboardDeleted (HTTP 410), so restore it before reading its history.

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

Fetch one historical revision.

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}$
revision
integer<uint64>
required

Revision number to fetch.

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

A historical revision with its full definition.