Odd values returning from API calls for time related keys

I have some very simple testing I’m doing where I just ask for a list of projects for a given workspace detailed here: https://docs.clockify.me/#tag/Project/operation/getProjects.

https://api.clockify.me/api/v1/workspaces/{workspaceId}/projects

This works. However, any keys returned that have to do with time are returning odd values. For example, duration looks like this duration: "PT22M42S" and estimate looks like estimate: "PT0S".

I couldn’t find anything about this in the documentation or Googling except one blog post by Clockify saying they fixed an issue like this back in December of 2021.

Anyone have any idea what’s going on here?

Maybe PT0S means Project Time 0 Seconds? Seems to be related to that in some way shape or form.

Project Time <VALUE> <TIME_UNITS>

So, PT40H would mean the project estimate is 40 hours. This is not documented anywhere and really not ideal.

Can we get a simple int value in minutes?

Hi @jeremiah

Thank you for using Clockify and welcome to our forum!

The ‘PT’ in the results for Estimate and Duration means ‘period of time’. This is a standard time format for duration according to ISO8601. There isn’t a way, at this time, to change that, I’m afraid.

I hope this clarifies it a bit, at least but don’t hesitate to ask if you have any further questions.

Cheers!

Thanks for the reply! I can work with that. The documentation doesn’t seem to match what I’m pulling in. Is there a chance the doc site is out of date?

Hi Jeremiah.

Could you let me know what do you mean by that - are you still referring to the time format, or is there a call that is shown in the documentation that is not working? If easier, you can reach out to us at support@clockify.me and we can look into this in more details.

The documentation is up to date in terms of which calls are available and such, but we are looking to update it in order to make it clearer and easier to use.