This article lists breaking API changes and provides guidance for how to handle the updates. Breaking changes are API updates that could cause client applications (such as custom integrations) to fail. Although we try to avoid making breaking changes, they are sometimes necessary in order to address critical issues, align API features with ongoing product changes, or improve API performance.
Before a breaking API change is made, affected customers will be notified in advance. Information about the breaking change will also be added to this article. If you have any questions, please reach out to your Client Success Manager or email firstname.lastname@example.org.
For a full list of API changes, including non-breaking changes, please see the Mavenlink Release Notes.
On July 5, 2022, the date format of several date properties within custom field value Subscribed Events will be changed to the ISO 8601 standard (e.g. "2022-05-18T12:34:29-06:00").
The following date properties will be affected:
created_atproperty which appears within
updated_atproperty which appears within
valueproperty which appears within
custom_field_valuesfor Date custom fields
The following event types will be affected:
If you are parsing any of the affected date properties, please update your logic to parse dates in the ISO 8601 format instead.
user_can_edit removed from default response of GET api/v1/time_entries and GET api/v1/expenses — February 14, 2022
After February 14, 2022, the
user_can_edit field will no longer be included in the responses of the
GET api/v1/time_entries and
GET api/v1/expenses endpoints by default. We are making this change to improve the performance of these endpoints.
user_can_edit field indicates whether the current user can edit a time entry or expense. This is a value that Mavenlink does not display in the UI, nor surface in any of our pre-packaged integrations. However, as a Mavenlink API consumer, you may have asked for this value in a custom integration that you created.
If you have a custom integration that relies on the
user_can_edit field, please check the following:
- Do you parse the
user_can_editJSON? If you are not currently parsing that field, you don’t have to do anything.
- If you are parsing the
user_can_editJSON, you have two options:
- If you are not using the value anywhere else in your code, stop parsing that field.
- Add the following parameter to any
GETrequest made to either