templates

Update Template

Update template name, description, goals, settings, or status.

For CHILD templates (parent_template_id IS NOT NULL), inherited fields are read-only — they live only on the parent. The backend SILENTLY STRIPS any inherited fields from the PATCH body and proceeds with the allowed fields (name, description, status, settings.skills). This is forgiving: the existing frontend save flow re-sends every field on every save, even when only skills changed. Returning 422 for those breaks the save UX. We log every strip so drift is observable.

Allowed on a child: name, description, status, settings.skills.

patch/v1/templates/{template_id}

Path parameters

template_idstring required

Request body

namestring nullable

descriptionstring nullable

statusstring nullable

is_defaultboolean nullable

learningsobject nullable

phases_enabledboolean nullable

intro_instructionsstring nullable

outro_instructionsstring nullable

default_usestring nullable

speaker_modelstring nullable

advisor_modelstring nullable

turn_detector_backendstring nullable

archetype_idstring nullable

Response

Successful Response

idstring uuid required

namestring required

descriptionstring required

goalsobject[] required

settingsobject required

session_briefstring

tldrstring

statusstring required

is_defaultboolean

phases_enabledboolean

phasesobject[]

intro_instructionsstring

outro_instructionsstring

default_usestring

created_atstring date-time required

updated_atstring date-time required

warningsobject[]

parent_template_idstring uuid nullable

inheritanceobject nullable

created_bystring uuid nullable

creator_namestring nullable

creator_emailstring nullable

speaker_modelstring nullable

advisor_modelstring nullable

turn_detector_backendstring nullable

archetype_idstring uuid nullable

conversation_countinteger

Changes

No recorded changes to this endpoint across all 1 revision of this API.