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

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

Introduced POST /milestonesPOST /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}DELETE /folders/, 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 PATCH /folders/{id}PATCH /folders/ for information.

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:

See the POST /tasks/{id}/assetsPOST /tasks//assets 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.

Added the following properties to the request body for PATCH /tasks/:taskld:

Introduced the PATCH /tasks/:taskId/steps/:stepId endpoint to update a task's specific step. For now, CMP only lets you update the step's due date through the due_at property in the request body.

Added an optional owner_id property to PATCH /tasks/:taskId, letting you update a task's owner.

Added the type field in the response body for the GET /work-requestsGET /work-requests, POST /work-requestsPOST /work-requests, and GET /work-requests/{id}GET /work-requests/ endpoints to indicate whether the assignee is a user or a team.

Added created_at to the response body for the POST /campaignsPOST /campaigns and GET /campaigns/{id}GET /campaigns/ endpoints.

Added the asset_ids_without_field_inheritance body parameter for the POST /work-requests/{id}/tasksPOST /work-requests//tasks endpoint, which you can use to disable field inheritance for specific assets when creating a task from a work request.

Introduced the GET /tasks/{task_id}/steps/{step_id}/sub-steps/{sub_step_id}/fields endpoint, which lets you fetch the fields of a task substep.

Updated the minimum file_size value for POST /v3/multipart-uploadsPOST /v3/multipart-uploads to 1 byte.

Introduced three endpoints to support multipart upload (uploading single files in multiple parts):

Introduced the POST campaigns/{id}/fields end point, which lets you add a field to a campaign.

Introduced the PUT /events/{id}/fields endpoint, which lets you replace existing fields of an event.

Introduced the POST /events endpoint, which lets you create an event.

Introduced the GET /userlist endpoint, which lets you fetch a list of users.