Skip to main content
POST
Create 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

Create a dashboard. The caller supplies the ID, so a retry after a timeout returns DashboardIDConflict rather than silently creating a second dashboard.

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}$
schema_version
enum<string>
required

Wire schema version; only dashboard.v1 is accepted.

Available options:
dashboard.v1
folder_id
integer<uint64>
required

Folder the dashboard is created in. Must be a folder the caller can write.

Required range: x >= 1
definition
object
required

Complete dashboard payload stored as a portable dashboard.v1 document. Unknown keys, duplicate keys, NaN/Inf, over-range numbers and trailing values are rejected; the serialized form must stay within 1 MiB.

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.