Delete task templates

Deletes multiple task templates from the space in a single bulk operation. Task templates are reusable task
definitions that can be instantiated into actual tasks. Deleting templates does not affect tasks already
created from those templates. The deletion is performed asynchronously and returns an operation ID for
tracking the deletion progress.

Key Features:

  • Efficiently deletes multiple task templates in a single API call
  • Removes template definitions and all their metadata including associations and custom properties
  • Does not affect existing tasks that were created from the deleted templates
  • Returns async operation ID for tracking deletion progress
  • Maintains audit trail of all template deletion actions
  • Processes deletions asynchronously for better performance with large batches

Authorization Logic:

  1. User must have a valid JWT token with management scopes
  2. User must have program update permissions
  3. User must have permission to manage all specified task templates

Usage Example:

Delete obsolete or unused task templates to clean up the workspace after reorganizing workflows, or remove
deprecated templates that are no longer part of current processes. For example, after updating your onboarding
process, delete the old onboarding task templates while keeping tasks already created from them.

Path Params
string
required
length between 7 and 22

The unique identifier of the space containing the target entity. This determines the scope of entity queries and ensures proper access control. The space must be accessible to the authenticated user with appropriate permissions. It can be the unique identifier (GUID) of the space or the word "default" to indicate the default programs space. Common values include "default" and "rkr83lapKkyCJuLLWqLqzB".

Body Params
ids
array of strings

Array of task or task template identifiers to be deleted in this bulk operation. Each ID must be a valid stable string identifier in base64url format (e.g., yT97zSH8tnz8OWxeVFzKTj). Provide between 1 and 100 IDs per request for optimal performance. All specified tasks must exist and the authenticated user must have delete permissions for each task. Used to target specific tasks for permanent removal from the workspace.

ids
boolean | null

Controls whether the deletion operation cascades to remove all descendant subtasks in the task hierarchy. When true, deleting a parent task will also permanently delete all nested child tasks and their subtasks recursively. When false or omitted, only the specified tasks are deleted while preserving their children as orphaned tasks. Use true for complete cleanup of task trees, false for selective parent removal during hierarchy restructuring.

Responses

Language
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json