Skip to main content
PUT
/
api
/
task-types
/
{id}
Update Task Type
curl --request PUT \
  --url https://api.example.com/api/task-types/{id} \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>",
  "projectId": 123
}
'
{
  "id": 123,
  "name": "<string>",
  "projectId": 123
}
Updates the name or project association of an existing task type owned by the authenticated user.

​
Authentication

Requires Bearer token authentication.

​
Path Parameters

​
id
integer
required
The unique identifier of the task type to update

​
Request Body

​
name
string
required
The new name for the task type (max 100 characters, cannot be blank)
​
projectId
integer
required
The ID of the project to associate this task type with

​
Response

​
id
integer
required
The unique identifier of the task type
​
name
string
required
The updated name of the task type
​
projectId
integer
required
The updated project ID

​
Example Request

curl -X PUT https://api.example.com/api/task-types/5 \
  -H "Authorization: Bearer YOUR_TOKEN_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Critical Bug",
    "projectId": 1
  }'

​
Example Response

{
  "id": 5,
  "name": "Critical Bug",
  "projectId": 1
}

​
Error Responses

​
400 Bad Request
Validation failed for the request body
{
  "error": "Validation Failed",
  "message": "name: must not be blank"
}
​
401 Unauthorized
Authentication token is missing or invalid
{
  "error": "Unauthorized",
  "message": "Invalid or missing authentication token"
}
​
404 Not Found
The task type or project does not exist, or does not belong to the user
{
  "error": "Not Found",
  "message": "Task type not found"
}

Build docs developers (and LLMs) love

Get started for freeTalk to us