Introduced PATCH /milestones/:id, which updates a milestone. All parameters in the request body are optional but not nullable. Only the provided fields are updated.

📘

Note

If the tasks array is empty, it removes all task associations for that milestone.

Introduced POST /tasks/{task_id}/urls, which lets you add a URL to a task. See the API reference for information.

Introduced POST /milestones, which creates a milestone. This defaults to the organization's campaign if campaign_id is omitted. This validates tasks against the selected campaign and ensures they belong to it.

Introduced DELETE /folders/:id, which lets you delete a folder, including all its assets. This is a soft delete that moves the folder to CMP's Recycle Bin.

Added the ability to assign teams to individual sub-steps within a task. All API endpoints that return the sub-step data of a task now include the assignee_type attribute, specifying whether the assignee is a user or a team.

Introduced PATCH /folders/{id}, which lets you update a particular folder's name or parent. See the API reference for information.

• Added template details to the work_request_added webhook event.
• Added the ability to filter the GET /work-requests endpoint by template_id, created_at__from, and created_at__to.

Updated POST /tasks/:taskId/assets to accommodate adding assets to tasks in different mechanisms. Previously, the API only let you add uploaded assets by providing the key and title of the asset. The updated API lets you fork an existing asset from the Library and add it to the task using the content guid of the Library asset.

A new type parameter has been added to the request body with these values:

• direct_upload - This is an asset uploaded using the upload assets endpoint.
• fork_from_library - This forks an existing asset from the Library and adds it to the task. The type field is optional and defaults to direct_upload if not provided.

📘

Note

Renditions is currently not supported for Library assets.

See the API documentation for the full request body details.

Added the users field in the response body for get-teams-by-id – GET /teams/{id}, which is an array of objects containing information for respective users in that team, such as ID, name, and email.

Introduced the GET /v3/events/:id/fields endpoint to fetch the list of fields for that event.