Create draft and patch document
Create a new draft on the published document and apply the patch. There is no auto-publish — the response includes the new draftIdentifier for follow-up calls. Pass an optional branchId to attach the draft to a branch; omit it for a draft on the main (unpublished) workspace.
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 published document's URL slug (e.g. abc123) or its canonical workbook UUID.
Body
The draft-route patch body plus an optional branchId selecting the branch the new draft is attached to.
Branch the draft is created on. Omit for a draft on the main (unpublished) workspace.
Immutable model identifier. Must match the document's current base model or the API will return a 400 error.
Immutable model identifier. Must match the document's current workbook model or the API will return a 400 error.
Document name.
1 - 254Document description.
Caller-supplied description of what this patch changes, written to the history audit trail. When omitted, Omni auto-generates one from the updated sections.
1 - 255Query presentations (tabs/tiles) keyed by record key.
Dashboard filters/controls keyed by control ID.
Document settings. Shallow-merged with the existing settings.
Container layout. When present, fully replaces the existing layout.
Response
Draft created and patch applied successfully.
Published document identifier the draft targets.
"def456"
Identifier of the draft the patch was applied to.
"abc123"
Document name.
"Blob Sales"
Document description.
"Overview of daily Blobs R Us Sales"

