Open wirduzen-felix opened 2 years ago
Just noticed, that the global api is also used by the app, so you can reverse most of the requests from there. Still, is there some kind of documentation somewhere?
Hi @wirduzen-felix, please note that global.api.clockify.me is our Devs team working API and this API is subject to change. This means that once we change something, the scripts will probably stop working. Therefore, we have public open API documentation for the calls that are not being changed that often, and even if we change something, that is being updated in the documentation as well.
@7saraK would it not be better to use the public API in this extension then?
Having a public+private API means that you can never be sure that the public API is usable. It's usually better to have a single API that you can easily extend.
Hi @wmertens, kindly note that our Devs recommended using our open API documentation for all the integrations you would like to create. Please see this link for more info. Hope it helps. If you have any additional questions feel free to ask, and I'll be happy to help as much as possible. Cheers!
Hi there, I just noticed that the clockify browser extension uses the global.api.clockify.me API internally. Sadly I can not find any documentation on that API. I can only find information about api.clockify.me/v1. Can someone maybe give me a hint on where to look or something? I wanted to access the Projects of a workspace filtered by customer from within the clockify extension. With api.clockify.me/v1 I would just call
GET https://api.clockify.me/api/v1/workspaces/WORKSPACEID/projects?clients=test
Sadly this endpoint answers with a 405 on global.api.clockify.meIs there any specific reason, why the extension uses global.api.clockify.me instead of api.clockify.me/v1?
Any help is much appreciated. Thanks in advance.