API Changes
This page contains a list of past and upcoming changes of our API. We try our best to prevent breaking changes, but sometimes we need them in order to release a new awesome feature πŸš€

Upcoming changes

In this section you find upcoming changes. Breaking changes are marked additionally 🚨

Project Templates - Auto Billability 🚨

Currently, projects have one property called IsBillableByDefault ,which decides whether time entries created on that project are marked as billable or not. This is either set by the project template, or if no project template was used for creation, by whether the project has a company or not. In the case of a company, the times are marked as billed, otherwise the times are marked as not billable.
The problem is, that the project template always overrules this company rule. We need to have more flexibility here, so we change the IsBillableByDefault property on the project template from a boolean to a string field with the possible values: on, off, auto.
When the auto option is set, the IsBillableByDefault of the project on project creation will be set according to the company rule, so true if a company is set and false if no company is set.

Multi-User Assignment - 18.09.21 🚨

This release adds the highly requested feature to assign multiple users to the same task. As a result, we reworked the endpoints that allow assigning multiple users to tasks and task templates as well as automations.
If you want to use this feature, please enable the task setting "Allow multi-user assignment" in awork in the workspace settings page. Alternatively, you can activate the setting by calling the tasks/settings endpoint from below with the setting name allow-multi-user-assignment.

Removed endpoints

1
POST /tasks/assignUsers
Copied!
1
POST /tasks/unassignUsers
Copied!

Added endpoints

post
https://api.awork.io/v1/
tasks/{taskId}/setAssignees
tasks/{taskId}/setAssignees
post
https://api.awork.io/v1/
taskTemplates/{tasktemplateId}/setAssignees
taskTemplates/{taskTemplateId}/setAssignees
post
https://api.awork.io/v1/
tasks/settings
tasks/settings

Changed endpoints

post
https://api.awork.io/v1/
tasks/batch/{operation}
tasks/batch/assignusers 🚨
Additionally, these automation models were changed 🚨
For the action assign-user-to-task, there is now an additional ActionValue removeOldAssignments. In order to assign multiple users to a task, you need the set this value to false. You can also add multiple assign-user-to-task actions to an automation in order to assign multiple users for a single trigger.
For the actions task-create-project and task-create-private, the task ActionValue now has an array assigneeIds instead of a single assigneeId. However, you cannot assign multiple users to private tasks.

Recent changes

This section shows you past changes that are already live in our API

Project Templates - 18.07.21 🚨

This feature is part of our big Einhorn release, which brought a bunch of awesome features and an updated UI framework πŸ¦„
Project Templates used to be the Project Types, which now have a secondary role, similar to the Type of Work found on Tasks, to make it easier to understand for our users and remove some restrictions like creating a project without a Project Template.
Due to these complex changes, we completely reworked the existing Project Type endpoints and added new endpoints for Project Templates.

Added endpoints

CRUD endpoints for project templates
get
https://api.awork.io/v1/
projectTemplates
projectTemplates
get
https://api.awork.io/v1/
projectTemplates/{projectTemplateId}
projectTemplates/{projectTemplateId}
put
https://api.awork.io/v1/
projectTemplates/{projectTemplateId}
projectTemplates/{projectTemplateId}
post
https://api.awork.io/v1/
projectTemplates
projectTemplates
delete
https://api.awork.io/v1/
projectTemplates/{projectTemplateId}
projectTemplates/{projectTemplateId}
Older changes can be found in the release articles on our roadmap https://www.awork.io/roadmap/ πŸ•΅πŸ»β€β™‚οΈ
Last modified 18d ago