-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
400 Forbidden Error when fetching last 24h data #4
Comments
Something has changed on Carelink.. Using the app i can now follow multiple people. This might be a big problem to fix. |
This started happening to me as well yesterday. Surely it is caused by an API change on the Carelink side. |
I can confirm that adding the "patientId" to the data request works. So as a quick fix we might consider just adding a new parameter to the However, a complete solution might be a bit more complex. In the xDripCareLinkFollower I see a lot of pull requests which implement the "Multi follow" feature. These would need to be ported to the carelink-python-client. |
If you want to implement the 'multi-follow' feature, I think in the issue you gave me previously they talk about a route (supposedly https://carelink.minimed.eu/patient/m2m/links/patients) that recovers all the linked patients for a given partner account. Anyway, thank you for your help. |
Hello ondrej,
I'm using this implementation since a few months now and it worked perfectly until this morning.
I can not manage to recover data from the API anymore and it gives me a 400 "Forbidden" error message.
After some research, it looks like the connection process is fine and that the error comes from this route: "https://clcloud.minimed.eu/connect/carepartner/v6/display/message"
Right now, we make a POST request to this route providing the auth token and a url-encoded form containing the username and the role but it seems like they have changed something with their API and that it needs something new.
So i was wondering if someone out there has the same problem and how can we find a solution for this ?
The text was updated successfully, but these errors were encountered: