Get document state
Read the document’s current state — the draft state if a draft exists, otherwise the published state. The response is structured so you can take it verbatim and submit it as the body of a draft PATCH (the round-trip contract).
Tiles in queryPresentations.data are keyed by a stable record key (e.g. "1", "2"); the server uses that key to identify existing tiles on a later patch, so you never need to track any other identifier. Control IDs and container instanceKey / referenceKey values also round-trip unchanged.
A workbook-only document (no dashboard layout yet) returns only the workbook-scoped fields (name, description, queryPresentations); the dashboard-scoped containers, controls, and settings are omitted until a layout exists.
Authorizations
Can be either an Organization API Key or Personal Access Token (PAT).
Include in the Authorization header as: Bearer YOUR_TOKEN
Path Parameters
The document's URL slug (e.g. abc123) or its canonical workbook UUID.
Response
Document state.
Current document (or draft) state. Round-trippable: submit this verbatim as a draft PATCH body. containers, controls, and settings are dashboard-scoped and omitted for workbook-only documents with no layout yet.
Document name.
254Document description.
Container layout array (grid / stack / page / reference containers, recursively nested). On a patch, when present this fully replaces the existing layout. The server validates the full structure on apply; container instanceKey / referenceKey values round-trip unchanged. See the dashboard layout reference for the complete grammar.