I've been using your script since February with no problems at all. Works very well and is indispensable for me as I only have Linux systems. As of this morning, I get the following error message when I try to use the script to even list the contents of the cloud: ☠ Client error: POST https://my.remarkable.com/token/user/new resulted in a 403 Forbidden response: You have been signed out. Please update your app to log in again. I get the same message if I try to "register" again. Any suggestions? Thanks, eric

I have scripts that use the metadata information to process the lines files from the tablet. It would be very helpful if the download, using the php script, could include the metadata file along with the others in the zip file created.

If I try to upload a PDF document, the PHP script seems to do the job but the tablet claims the document is corrupt when it downloads from the cloud. The "list" however seems to show that the documents are stored in the cloud (although if no "to" was given on the upload, they are placed in a separate folder named with the UUID of the document). Happy to provide more details if desired.

Downloading (which is my main use case for your code) works very well indeed. Thank you!

Hi, I did few tests in the past days with these api but all of a sudden since yesterday the authentication endpoints started to respond in html instead of normal string responses. I did my tests with Insomnia client, did not change the requests and everything was working fine but when I resumed my work yesterday I started to receive these html response (of which the rendered preview is empty).

The other endpoints seem to respond as usual.

Am I doing or did I do something wrong? Anyone else facing the same problem?

Thanks, Nik

The command line tool crashed with:

☠ Unknown ID trash. Inconsitent meta data

I think it's because I have deleted a file on the reMarkable2. It's a bit difficult to test, sorry about that.

The --loglevel debug shows:

-> GET https://document-storage-production-dot-remarkable-production.appspot.com/document-storage/json/2/docs
<- Status 200 5705 bytes
[
 ...
    {
        "ID": "c2a07c8d-2fa1-47ec-9522-b178f88f443e",
        "Version": 2,
        "Message": "",
        "Success": true,
        "BlobURLGet": "",
        "BlobURLGetExpires": "0001-01-01T00:00:00Z",
        "ModifiedClient": "2020-12-25T11:21:56.481481Z",
        "Type": "DocumentType",
        "VissibleName": "redacted.pdf",
        "CurrentPage": 0,
        "Bookmarked": false,
        "Parent": "trash"
    },
...
Exception caught in /home/ohad/dev/ReMarkableAPI/src/RemarkableFS.php:165
#0 /home/ohad/dev/ReMarkableAPI/src/RemarkableFS.php(176): splitbrain\RemarkableAPI\RemarkableFS->calcPath('trash')
#1 /home/ohad/dev/ReMarkableAPI/src/RemarkableFS.php(50): splitbrain\RemarkableAPI\RemarkableFS->calcPath('c2a07c8d-2fa1-4...')
#2 /home/ohad/dev/ReMarkableAPI/src/RemarkableFS.php(28): splitbrain\RemarkableAPI\RemarkableFS->refreshIndex()
#3 /home/ohad/dev/ReMarkableAPI/remarkable.php(117): splitbrain\RemarkableAPI\RemarkableFS->__construct(Object(splitbrain\RemarkableAPI\RemarkableAPI))
#4 /home/ohad/dev/ReMarkableAPI/remarkable.php(73): Remarkable->cmdList()
#5 /home/ohad/dev/ReMarkableAPI/vendor/splitbrain/php-cli/src/CLI.php(131): Remarkable->main(Object(splitbrain\phpcli\Options))
#6 /home/ohad/dev/ReMarkableAPI/remarkable.php(225): splitbrain\phpcli\CLI->run()
#7 {main}

Hey, I'm trying to authenticate a custom script of mine, but I'm having some issues. Here's my code

import requests

r = requests.post(
    "https://my.remarkable.com/token/json/2/device/new",
    data={
        "code": "<code>",
        "deviceDesc": "desktop-windows",
        "deviceID": "<uuid4>",
    },
)

When I run this I get a response with a code of 400 and the text "Failed to decode POST body as JSON".

Has the API changed?

Thanks for the awesome writeup.

Bumps guzzlehttp/guzzle from 6.5.5 to 6.5.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps guzzlehttp/guzzle from 6.5.5 to 6.5.6.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Has the API been updated by reMarkable?

I've been working on a Ruby API wrapper and am running into issues with user token endpoint. The device token endpoint is working correctly, but when I attempt to use that token to fetch / refresh a user token, I get a 400 with the message "You must connect a rM device in the webapp before you can use this service."

However, when I check the web interface, a new app has been created.

I also attempted to register a device with rmapi and am getting similar issues.

Ideas?

I started getting this error:

$ ./remarkable.php list
☠ Client error: `GET https://document-storage-production-dot-remarkable-production.appspot.com/document-storage/json/2/docs` resulted in a `401 Unauthorized` response:
Serving request failed, Msg: invalid token: token contains an invalid number of segments: invalid token, Origin: invalid (truncated...)

This error might be related to the recent software update (release 2.7).

Hi, thanks for the detailed writeup!

I see that the token given out by rM is, in fact, a JWT token that has an "auth0-userid" field. Is it a real user ID that's unique (and same) for every user?

For instance, mine is auth0|5f634d3c591dce00704a9822; I don't have a second rM account to see if it's different for other users.

Do you also experience errors 500 when trying to use the API? I get a 500 for any request on https://document-storage-production-dot-remarkable-production.appspot.com. Do you know if the team at reMarkable upgraded their internal API and left this one behind?

Btw, their service manager returns the same service URL as before when queried:

$ curl "https://service-manager-production-dot-remarkable-production.appspot.com/service/json/1/document-storage"
{"Status":"OK","Host":"document-storage-production-dot-remarkable-production.appspot.com"}

As the title suggests, I am unable to successfully call any endpoint - even after I call remarkable.php register <valid-registration-code>.

This may even be an issue with the overall usage of remarkable's endpoints, as I have been unable to call their endpoints directly.

Steps to reproduce:

1. Query for a new token:

   		GET: https://webapp-production-dot-remarkable-production.appspot.com/token/json/2/device/new`
   

   		 { 
   		      "code": "fuzzbuzz",
   		      "deviceDesc": "desktop-windows",
   		      "deviceID": "160022F6-EA84-42C7-B413-C1F5C6C3112F"
   		 }
   

2. Fetch a refresh token:

   		POST: https://webapp-production-dot-remarkable-production.appspot.com/token/json/2/user/new
   		--header 'Authorization: Bearer eyJ...'
   

3. Take the token from step 2, and validate the document endpoint:

   		GET: https://service-manager-production-dot-remarkable-production.appspot.com/service/json/1/document-storage?environment=production&group=auth0%7C5a68dc51cb30df3877a1d7c4&apiVer=2
   		--header 'Authorization: Bearer eyJ...'
   

   Which returns

   		{
   		      "Status": "OK",
   		      "Host": "document-storage-production-dot-remarkable-production.appspot.com"
   		}
   

4. Take this endpoint, and query the docs endpoint

   		GET: https://document-storage-production-dot-remarkable-production.appspot.com/document-storage/json/2/docs
   		--header 'Authorization: Bearer eyJ...'
   

   Which returns a 401: Unauthorized status code. What am I missing?

I'm trying to update a PDF document. When I send the new version of the pdf document I'm making sure to update the version and the ModifiedClient metadata. So far I can see the updated pdf on the mac and android apps. But the PDF on the remarkable tablet stays the same, even after trying manual sync on settings -> storage -> check cloud sync.

If I draw on the non updated PDF on the tablet. It brings back the old version on all devices.

Is there a way to make sure the tablet downloads the latest version as well? Has anybody has updated a PDF successfully?

I'm testing on the Remarkable 2 on version 2.6.2.75

update: Same Issue with version 2.7.0.51

When uploading a file with the command like this: remarkable.php upload /path1/path2/path3/filename.txt the script correctly creates all the directories path1->path2->path3 with the name inside path3. This worked excellent.

But then I tried to delete "path1" directly, without deleting the sub-directories. This delete is not "recursive", so the sub-directories seem to still exist, and then seems to lead to some corruption. When I tried to run the "remarkable.php list"-command, it gave an error message about wrong metadata (Don't remember the exact error message)

But if I deleted all the path2, path3 and the file inside path3, the list-command worked again, and it seems that I cleaned everything up.

=> Please consider one of two options:

1. Don't allow to delete directories that are not empty
2. Make the delete-command recursive to delete everything

Else, love the php-"app"!

According to https://github.com/juruen/rmapi/issues/23#issuecomment-425832548 you may now provide your own user agent string.

I guess it is about this... https://github.com/splitbrain/ReMarkableAPI/blob/5eafff7a50981d59d0f5a05712b11e210842210c/src/RemarkableAPI.php#L69