Help and Support » FAQ

Status of the API refactoring

Since we get frequent questions about the status of the API refactoring, we now summarize the current status here:

Status Update

Status: 2023-08-19 Because of personal issues and a lot of support requests in the last weeks we did not had time to fix the last issues. Status: 2023-07-30 Still working on it. Having some problems with timezones.

Status: 2023-06-29 Still working on it and did a good process on the whole development.

Status: 2023-06-27 Restarted work on the API. Quite frustrating that it takes so long, but it needs time.

Status: 2023-03-21 Still work in progress.

Status: 2023-02-26 Because of sickness, a lot of support requests and coding other features currently no further update.

Status: 2023-02-08

Because of sickness no further updates on this. The progress on replacing the old third party library are already almost done and just need fine tuning.

Status: 2023-01-22

One big change what is missing is replace an old library we are still using. As that library is the main part of the authentication of the third party library this is quite a big task as we will replace some parts of the replacement with a custom solution we need.

Status: 2023-01-20

Currently Michael is testing through the different endpoints, verifying that before/after the API works the same. So far it looks already quite good, but we need to test everything completely as there will be no point of return after the deployment. Especially the documentation of the endpoints (even if relatively automatically created) has to be gone through.

General information

Since we are not only trying to take into account the wishes that have come together at, but also technically to make the API a bit cleaner and at the same time keep it backwards compatible, the programming, documentation and especially the testing takes significantly longer.

This concerns the "Personal API" as well as the Third-Party API.

The following topics will be possible as soon as the programming is finished and the refactoring has gone live:

  • Personal tokens can be "scoped" and do not have access to all endpoints immediately.
  • Third party apps can also be scoped more accurately and can get more access. Among other things, also read.
  • HRV values can be saved with the different units (important for e.g. the iOS app Healthfit)
  • Missing endpoints around Daily Notes, blood glucose, body temperature will be included

In a later step these wishes will be implemented:

  • Extend Personal API to allow to set tags, equipment, sport type&subtype during upload
  • Reading activities (including data streams). This point will take some time, because an activity includes a lot of data.

Related articles

Didn't find an answer to your question?

Please let us know if you have wishes or have encountered bugs. We give our best to make Runalyze as good as possible for you. - Therefore we would be interested in your suggestions for improvement. In general most questions, problems and ideas are more appropriate to ask in the forum.