Skip to main content
POST
Create dashboard

Restrictions

Usage

  • dashboard_id is chosen by the caller and must be a canonical UUIDv7. Reusing an ID that already exists returns HTTP 409 DashboardIDConflict.
  • Every application a definition reads must exist in the account and be readable by the caller, otherwise the call fails with InvalidParameter or AccessDenied.
  • A failed definition validation returns HTTP 400 with up to 20 violations, each naming a path, a rule and a message, and the first one repeated as the error message.
  • Unknown request fields are rejected: the body is decoded strictly, so a typo fails with InvalidParameter instead of being ignored.
  • A body over 2 MiB, a definition over 1 MiB, or exceeding a count limit returns HTTP 413 EntityTooLarge; a schema_version other than dashboard.v1 returns HTTP 422 UnsupportedSchemaVersion.

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

Create request. The caller supplies the dashboard ID, so a retry with the same ID is rejected as a conflict instead of creating a duplicate.

dashboard_id
string
required

Dashboard ID to create, 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}$
schema_version
enum<string>
required

Wire schema of the definition. Must be dashboard.v1.

Available options:
dashboard.v1
definition
object
required

The dashboard body: title, default time range, variables, and tabs. A dashboard is capped at 10 tabs, 100 panels and 300 queries. A tab holds at most 30 panels and 100 queries, top panels and sections together.

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 dashboard as stored, including its current definition and revision.