When creating a task, it is now possible to send assign_default_workers parameter.

If the param is sent as true, we prioritize default workers set at the template level. If template level default workers do not exist, we will use the department level. Both are set per property.

Default assignees will be adjacent to assignments that were manually set. So if you send custom assignments, and also send assign_default_workers=true we will honor both.

We have published a new endpoint for subdepartments and their corresponding Ids. The subdepartment_id will be used when creating a task.

[
    {'id': 101, 'name': 'Human Resources'},
    {'id': 242, 'name': 'Marketing Analytics'},
    {'id': 317, 'name': 'Customer Support'},
    {'id': 455, 'name': 'Product Development'},
    {'id': 528, 'name': 'Financial Planning'}
]

Create task / Update task

Added the following fields as values that can be used to create or update a task:

• subdepartment_id
  • See new subdepartment endpoint here
• rate_paid
• rate_type
• requested_by

Request Updates

---

List tasks / Retrieve task

Added the following fields to the task response:

• billable [boolean]

Added the following fields to the task response and task list response:

• assignments[].employee_code [string]
• subdepartment [object]

Response Updates

Added the following fields that can be used when retrieving tasks in bulk:

• assignee_ids [delimited list of integer values]

Added API resources to manage property contacts

• Create company contact
• Update company contact
• Delete company contact
• Retrieve company contact

Added the following details to the Task Webhook payload:

1. Task Report URL (task_report_url)
2. Bill To (bill_to)
3. Company ID (company_Id)