---
title: "Remove dependencies from a task by Id"
method: POST
path: "/1.0/tasks/{taskId}/remove-dependencies"
tags: ["Tasks"]
---

# Remove dependencies from a task by Id

`POST /1.0/tasks/{taskId}/remove-dependencies`

## Path parameters

- `taskId` integer, required

## Request body

- TaskDependencyPublicAPI
  - `dependencies` TaskDependencyPredecessorPublicRequest[], required — Task Dependencies allow you to define relationships between tasks that are dependent on each other.
    - `taskId` integer — The task's unique, system-generated **identifier**, which can be used to identify the task globally

## Response `200`

The requested action was successfully executed.

- TaskPublicDependenciesAPIResponseEntity
  - `taskId` integer — The task's unique, system-generated **identifier**, which can be used to identify the task globally.
  - `taskName` string — The **name** of the task.
  - `taskDescription` string — The `description` of the task. The description body needs to be in **html** format to avoid any formatting issues in the application.
  - `startDate` string — The date when a task starts its execution. It can be empty. The format for the start date is _YYYY-MM-DD_.
  - `dueDate` string — The date when a task completes its execution. It can be empty. If both `startDate` and `dueDate` are specified for a given task, it is necessary that the latter should be on or after the given `startDate`. The format for the due date is _YYYY-MM-DD_.
  - `archived` boolean — The field `archived` denotes whether the task is archived or not. The task if archived will not be available in all search requests.
  - `effortInMinutes` integer — The effort is the expected time required to complete the task. The value is determined in minutes.
  - `progress` integer — The task's progress, if indicated, will be available here and ranges in value from 0 to 100. The task's status can be used in place of this field, however progress can offer more precise data.
  - `atRisk` boolean — Indicates whether the task has been marked as At Risk. This parameter is used to indicate that immediate action is necessary to unblock the task's execution.
  - `createdAt` integer — The time when the task was created. The referenced time will be in epoch millis.
  - `updatedAt` integer — The time when the task was last updated. Any changes that's related to the task are captured and specified here in epoch millis.
  - `createdBy` TaskCreatedByUserPublicAPI — The team member who updated the task.
    - `emailId` string — The user's email identifier.
    - `userId` integer — The unique identifier for the user.
    - `firstName` string — The first name of the user.
    - `lastName` string — The last name of the user.
  - `updatedBy` TaskCreatedByUserPublicAPI — The team member who updated the task.
    - `emailId` string — The user's email identifier.
    - `userId` integer — The unique identifier for the user.
    - `firstName` string — The first name of the user.
    - `lastName` string — The last name of the user.
  - `project` ProjectPublicAPITaskResponseEntity — The `project` associated with task.
    - `projectId` integer — The project's unique, system-generated identifier, which can be used to identify the project globally.
    - `projectName` string — The name of the project.
  - `status` TaskStatusPublicResponse — The task status value and the label. v 10, l xyz.
    - `value` integer — The value of the status field is the unique identifier for status fields.
    - `label` string — The label is the name of the status.
  - `fields` TaskFieldPublicResponseAPIEntity[] — Fields lists the custom project fields whose values were provided during project creation or updated later. Refer these [examples](https://developer.rocketlane.com/v1.0/docs/custom-fields#examples-of-requests-and-responses-for-assigning-custom-field-values) to know more about different types of custom fields returned in response.
    - `fieldId` integer — The unique identifier for the field.
    - `fieldLabel` string — The label of the field.
    - `fieldValue` object — The `fieldValue` is the value provided while creation or updating. The fieldValue can be a string, an integer, or an array and it must match the type of the field. Refer [e xamples](https://developer.rocketlane.com/v1.0/docs/custom-fields#examples-of-requests-and-responses-for-assigning-custom-field-values) to know how each `field_type` is associated with task.
    - `fieldValueLabel` string — The `fieldValueLabel` is the value provided while creation or updating in a String format.
  - `dependencies` TaskPublicLiteAPIResponseEntity[] — Task Dependencies allow you to define relationships between tasks that are dependent on each other. Note: Rocketlane allows you to have finish to start task dependencies. This means that dependent tasks are meant to start after the dependencies are marked as Complete.
    - `taskId` integer — The task's unique, system-generated **identifier**, which can be used to identify the task globally.
    - `taskName` string — The **name** of the task.
  - `private` boolean — This depicts if the task is private or not.

## Other responses

- `400` — This error typically happens when the request payload contains an error. If you want to make sure that the request's parameters are named correctly and are the right data types, you can examine the request's syntax.
- `401` — You see this error when trying to access this resource without being authenticated. Check the API request header to make sure it is not empty and has a valid api-key that you acquired from the Rocketlane API Settings tab.
- `404` — If we were unable to locate the resource you were looking for or the proper API endpoint you were looking for, this error would show up.

---

[API](https://skmtc.net/rocketlane/apis/rocketlane-api.md) · [All operations](https://skmtc.net/rocketlane/apis/rocketlane-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/rocketlane/rocketlane-api/revisions/1e8ba619e741/schema)