Publish a draft (new workflow or edits to a live one)
Changed onPublish the caller's draft.
For a brand-new-workflow draft this is the "Save workflow" action: full validation (at least one step, at least one Vision step, every agent and its parameters valid, pass criteria within range), org name uniqueness, and the plan's workflow cap (the only place a new draft is counted). The row flips from draft to active and normal versioning begins.
For an edit draft (staging changes to an existing live workflow) the draft's steps are applied to the parent as a new snapshot version, its metadata and reference images overwrite the parent's, and the draft is discarded. No cap is consumed (the parent already counts). If the parent has been published again since the draft branched, this returns 409 draft_base_outdated so the author can overwrite (retry with force=true) or discard, rather than silently dropping the newer version. Either way a validation failure leaves the draft intact to fix and retry.
Request
- Base URLhttps://api.ai.vision.tiliter.com
- AuthAPI key in header X-API-Key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Query parameters
Publish an edit draft even though its workflow has been published by someone else since the draft branched, overwriting their version.
Response
Successful Response
Example response
{
"steps": [
{
"name": "Overview shot",
"workflow_note": "Stand back and capture the whole subject in frame.",
"operator_reference_file_urls": [],
"agent_id": "object-detection-v1"
}
]
}Changes
- info
added the optional property
to the response with the status
- info
- warning
added the new
barcodeenum value to the//response property for the response status - info
added the optional property
/to the response with the status - info
added the optional property
//to the response with the status
- warning