Last weekend (and for the last many years) this was returning an amount and rate in a sub-object for each time entry - this weekend that is missing. No mention of this change in the docs that I can see - though docs for what gets returned are a bit “meh” anyway. But it was there, now it isn’t so my scripts that looked at that are failing - I’ve fixed my script by just not processing these and will need to use the time to work out the amounts myself - but it should at least be recorded as a change in the documentation.
Hi @JamesHorsley Thank you for reaching out to us!
I understand that there might be some confusion about the missing amounts, and I’ll gladly clarify this further for you.
Please note that we have updated the Free plan and starting this June 15th, Billable rates are now part of the Basic plan. (Date may vary depending on the number of users in a workspace)
As a business scales, some changes become necessary. Maintaining the old free plan features for all users was no longer possible if we want to keep the app fast and improving.
To continue innovating (like our upcoming features on roadmap, and more) and providing the high-quality service everyone can rely on, we’ve had to make our Free plan more sustainable which includes moving some features to the paid plans.
We also sent out an in-app notification to make sure our users are aware of these changes. For more information you can check out this page Learn more about the changes.
I have also passed this feedback to my team to double-check the documentation.Thank you for understanding! If you have any questions, please feel free to contact us and we’ll be more than happy to assist you directly.
I gathered it was probably related to that change … but your API documentation has a section to list breaking changes - and clearly this is a breaking change - I know that because it broke a routine I have to download data from the reporting API - sadly your docs are not on Github so can’t accept user pull requests when they are wrong but the issue here really is that as a side effect of the plan changes you are introducing breaking changes on the API and not documenting them.
1 Like
I just wanted to add that I would be interested in contributing to the API docs if they were on Github or something similar.
Thank you both @JamesHorsley and @Jesudas for the offer and feedback!
I have forwarded this to my team for their consideration and escalated the breaking changes section on the API documentation for closer inspection.
If there’s anything else we can help you with, don’t hesitate to reach out and let us know! Cheers!