# Task Statuses

Custom task statuses can be created to be used on tasks (stories). Custom task statuses are associated to task status sets, which can be applied to projects (workspaces).

## Fetching a list of Custom Task Statuses

 - [GET /custom_task_statuses](https://developer.kantata.com/kantata/specification/task-statuses/get-custom-task-statuses.md): This endpoint returns structured Custom Task Status objects.
As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array
and will be indexed by ID in the custom_task_statuses top-level JSON key.
Please see our Response Format section for more information.

## Creating a new Custom Task Status

 - [POST /custom_task_statuses](https://developer.kantata.com/kantata/specification/task-statuses/create-custom-task-status.md): Adds a new custom status to a task status set.

This endpoint returns structured Custom Task Status objects.
As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array
and will be indexed by ID in the custom_task_statuses top-level JSON key.
Please see our Response Format section for more information.

## Fetching a single Custom Task Status

 - [GET /custom_task_statuses/{id}](https://developer.kantata.com/kantata/specification/task-statuses/get-custom-task-status.md): This endpoint returns structured Custom Task Status objects.
As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array
and will be indexed by ID in the custom_task_statuses top-level JSON key.
Please see our Response Format section for more information.

## Updating an existing Custom Task Status

 - [PUT /custom_task_statuses/{id}](https://developer.kantata.com/kantata/specification/task-statuses/update-custom-task-status.md): Updates a custom task status. The name and position in the task status set can be updated. The status cannot be moved to a different status set and the category cannot be changed.

This endpoint returns structured Custom Task Status objects.
As with all Kantata OX API endpoints, the returned data will be referenced in sorted order in the results array
and will be indexed by ID in the custom_task_statuses top-level JSON key.
Please see our Response Format section for more information.

## Deleting an existing Custom Task Status

 - [DELETE /custom_task_statuses/{id}](https://developer.kantata.com/kantata/specification/task-statuses/delete-custom-task-status.md): Deletes a custom task status within a task status set. If assigned to a task (story), the task’s status will default to the status type (category)—not started, started, needs info, or completed.
- This will delete the task status from this set. If this status is currently being used by a task in a project, the status will reset to its default status type: Not Started, Started, Needs Info, or Completed.


The response will contain no content and an HTTP 204 status code if the request was
successful, or a standard Kantata OX error message explaining why the object could not be deleted.