Task templates

Four routes call the corresponding tasks.Template.* Bitrix24 methods. The API key needs the task or tasks scope; writes need a write-enabled key. The native Bitrix24 result is returned in data without conversion.

Method and path	Bitrix24 method	Parameters
POST /v1/task-templates	tasks.Template.add	JSON { "fields": { ... }, "params"?: { ... } }
GET /v1/task-templates/:templateId	tasks.Template.get	optional query params
GET /v1/task-templates	tasks.Template.list	optional query params and start
PATCH /v1/task-templates/:templateId	tasks.Template.update	JSON { "fields": { ... }, "params"?: { ... } }

add returns the numeric template ID. Fields are forwarded unchanged. The path templateId is a positive integer. get and update may return false under the native Bitrix24 contract.

For GET, pass params as a URL-encoded JSON object, for example ?params=%7B%22filter%22%3A%7B%22CREATED_BY%22%3A42%7D%7D&start=0. Native filter, select, and other Bitrix24 parameters can go inside params. start is passed separately to Bitrix24 pagination. list preserves the named data.task_templates collection, with templates keyed by ID. If Bitrix24 provides total or next beside result, they appear as meta.total and meta.next. For another page, repeat the request with start=meta.next; the wrapper does not fetch all pages automatically.