Create one task for each task type of the list. The project must use each task type. For an asset, the workflow of the asset type must also have each task type. If the list is empty, the route uses all the task types that are valid for the entity. If a task with the same task type exists, it is skipped. Clients and vendors cannot use this route.
POST
/data/entities/{entity_id}/tasks
curl \
--request POST '/api/data/entities/a24a6ea4-ce75-4665-a070-57453082c250/tasks' \
--header "Authorization: $API_KEY" \
--header "Content-Type: application/json" \
--data '{
"task_type_ids": [
"b24a6ea4-ce75-4665-a070-57453082c250"
]
}'
Request example
{
"task_type_ids": [
"b24a6ea4-ce75-4665-a070-57453082c250"
]
}