Changed authentication url, now matching rmapi authentication#35
Changed authentication url, now matching rmapi authentication#35maximiliankir wants to merge 1 commit intosubutux:masterfrom
Conversation
|
Can confirm that this resolves If need be, you can monkeypatch this fix into a version of rmapy pulled from pip using: import rmapy.const
rmapy.const.AUTH_BASE_URL = "https://webapp-prod.cloud.remarkable.engineering"
rmapy.const.DEVICE_TOKEN_URL = rmapy.const.AUTH_BASE_URL + "/token/json/2/device/new"
rmapy.const.USER_TOKEN_URL = rmapy.const.AUTH_BASE_URL + "/token/json/2/user/new"@subutux please merge! :) |
|
Thank you so much for theses URL that unblocked me :) |
|
@kurt-rhee I ended up using a combination of rmapy and the |
|
Wow that is amazing. Your repository is actually what I want to do as well (though I have much less experience than you writing software) Would you be willing to teach me how to use it? I could write some documentation and submit as a PR if you would like. |
|
@kurt-rhee if you're curious in how to use remarkable-substack I just added a readme file to that repo with the setup instructions. If you just want to build something to hit the API, you should be able to take the remarkable.py script as a guide -- just make sure you have the |

Fixes authentication error. Before this fix the remarkable cloud servers responded with "500: internal server error", when calling
register_device(code).