Web API changes: concise changelog?

[SunsetRunner]

Hi all,

I got an automated mail, notifying me "We’re also making changes to the Fitbit APIs to align with the Fitbit Platform Developer and User Data Policy".

Other providers and platforms usually provide some sort of changelog where one at once can see, what exactly changed -- her at FitBIT's I am unable to find such a changelog.

Does anyone know of a clear and concise documentation of those changes?

[Gordon-C]

Hi @SunsetRunner 

The Fitbit Platform Developer and User Data Policy is a brand new policy and there would not be a change log.  The Platform Terms of Service (PToS) are being changed to include reference to the Platform Developer and User Data Policy.  We released the changes to the PToS that supported the new policy, but needed to roll it back due to an error.   The current PToS, dated July 31, 2021, is still in affect.  The Platform Developer and User Data Policy will not be enforced until August 2022.  We typically don't provide a change log to updated policies.  Instead, we provide a link to the previous policies.  If you can provide an example of another company who provides a change log that is helpful, please provide message me that link.   I'll see if we can manage something similar at Google.

If you have other questions, please let us know.

Gordon

[SunsetRunner]

Please, read my question carefully!

I was quoting the bit about "changes to the Fitbit APIs" -- and that exactly is my question about: the API changes!

[Gordon-C]

We typically don't provide a change log to updated APIs.  Please message me with an example of another company who provides a change log that is helpful, and I'll see if we can manage something similar at Google.

[SunsetRunner]

Are you kidding me? There are only very few APIs I have to work with that don't and FitBIT is actually the only that doesn't even put a date(!) on its docs, let alone version it.

And are you seriously telling me you either don't know how to document API changes in a user friendly way, or would only do it if somebody else does it already?

Here's a thought:

Don't you think it important to help and support the people that are actually supposed to make your ecosystem attractive?

Oh wait, I know the answer:

---

@Gordon-C wrote:

We typically don't

---

[Gordon-C]

I was simply asking for an example that you like.  I will create a ticket for your request.