The endpoint GET /api/v2/sales/sales/{?id} will also return the key linked_projects. This contains an array with some info about the projects that are linked with the sale. linked_projects. This contains the following keys:
id of the project
name of the project
project_number of the project
created_at the date when the project was created. It has the YYYY-MM-DD HH-MM-SS format
project_status:
id of the project status
label of the status
color of the status
POST /api/v2/projects/assignment now returns the id of the created record instead of a list of all records.
The endpoint GET /api/v2/hrm/leave will also return results without leave status.
Fixed inconsistencies in handling referenced entities. Referencing an invalid entity will now consistently result in a 400 Bad Request error. Affected endpoints are:
The fields is_editable and is_deletable are only included in the API response when explicitly requested via the select parameter. Affected endpoints are:
Previously the application erroneously returned "501: not implemented" status codes. These cases have been updated to more appropriate status codes. Most of these cases are now returning a "404: not found" status code.
In the new project service UI, you can set a specific registration timeframe. Several API calls have been updated to return the correct start_date and until_date for services. Affected endpoints are:
Add is_active property to a sale service resource indicating whether it was successfully created for endpoints:
GET /api/v2/sales/service
Contract change for POST /api/v2/projects/service
Newly created project services no longer contain the hour_types of the provided default service by default. You can still provide the hour_types you want to add to the service in the body.
In the GET /api/v2/hrm/absence endpoint:
The end_date field is empty when the absence is ongoing.
The field absence_ongoing indicates whether the absence is ongoing.
Add copy_latest_quote property when cloning sale to indicate if the last quote on the original sale should be copied
POST sales/sales/{id}/duplicate
Update the input types for POST /api/v2/customfields/option:
Updated GET api/v2/crm/organization with extra field
Added CustomerGroup value option
Updated GET api/v2/sales/salesreason
Added blocked property to response
Updated GET api/v2/sales/salesfilters with options that can be used to filter GET api/v2/sales/sales
Added opportunityprogress value options
Added administration value options
Added responsible_person value options
Updated PUT api/v2/sales/sales
It is now possible to change the relation of a Sales entity from an Organization to a Person or from a Person to
an Organization with person_id or organization_id respectively
Added 'is_active' (bool) to Person, Organization, and ContactPerson
models (/api/v2/crm/person, /api/v2/crm/organization and /api/v2/crm/contactperson)
Added separate model for updating assignments (PutAssignment) (PUT /api/v2/projects/assignment)
PutAssignment no longer accepts 'start_date' and 'end_date' properties; you can no longer modify dates through the
API (PUT /api/v2/projects/assignment)
Added 'start_date' and 'end_date' to PostAssignment specifically (POST /api/v2/projects/assignment)