Bind a tile to a query model
Changed onBind a query-presentation tile to a query model on a draft.
The query-model binding (query.model_extension_id) is server-owned on the whole-document PATCH surface — a supplied value there is ignored and the tile keeps its stored binding. This draft-scoped route is the way to change it, addressing one tile by its stable record key. The binding shifts on every draft (each draft re-clones its query models), so work against a draft you have already read.
The queryModelId must be a live query model layered on this draft’s workbook model, and not already bound to another tile — a query model is dedicated to a single query. A LINKED tile inherits its query model from its source and can’t be bound directly.
Request
- Base URLhttps://omniapp.co (the document declares no server; this is the origin it was published from)
- URLhttps://omniapp.co/api/v2/documents/{identifier}/draft/{draftIdentifier}/queries/{queryKey}/query-model
- AuthHTTP bearer
Path parameters
Draft workbook identifier (see PATCH /api/v2/documents/{identifier}/draft).
Published document identifier.
Record key of the tile, as it appears in queryPresentations.data.
Request body
Response
Tile bound to the query model; the response carries the draftIdentifier.
Changes
- info
endpoint added
- info