Clone Job To Template V1
Promote a job’s configuration into a reusable template. Captures params minus the per-call fields (instruction, idempotency key, etc.) into the new template’s…
POST
Promote a job’s configuration into a reusable template.
Captures
params minus the per-call fields (instruction, idempotency
key, etc.) into the new template’s defaults. Useful workflow:
iterate on a one-off /trigger call until it works, then
clone-to-template to make it the team’s reusable starting point.
Reserved per-call params NOT carried into defaults:
instruction (unless include_instruction=true), tags,
webhook_url, webhook_secret, output_schema. Everything else
(model, effort, max_cost_usd, custom params) is preserved.
Path parameters
string (uuid)
required
Request body
CloneJobToTemplateRequest
string
required
Template name. Same rules as
POST /templates: alphanumeric + underscore + dash, must not collide with a built-in or an existing tenant template.string
required
Human-readable purpose; surfaces in
GET /templates.boolean
When true, the source job’s
instruction is captured as a template default. Most callers want false (the instruction is per-call, the template captures the surrounding config).Response
TemplateInfo
string
required
The exact string to pass as
agent_type on /trigger.string
required
builtin ships with the platform; tenant is owned by your org.string,null
Human-readable description (tenant templates only).