Skip to content
This repository was archived by the owner on Dec 11, 2025. It is now read-only.

Service Discovery

Jump to bottom
Gabor Veres edited this page Apr 8, 2019 · 3 revisions

Not all URLs are hard coded in the clients. Instead a Service Discovery API is used to fetch the hosts that should be queried.

All requests need to be authenticated with a Bearer authentication header.

Storage

To figure out where the storage API requests should go to a GET request is sent.

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

The query parameters are as follows:

  • environment should be production, there are probably other values for internal tests
  • group I am not sure what this is. It seems to always be auth0|5a68dc51cb30df3877a1d7c4. It might be related to auth0.com - a 3rd party authentication provider. The ID might be some auth0 internal identifier.
  • apiVer the API version. Note that the base URL has a 1 while this is 2

Notifications

GET https://service-manager-production-dot-remarkable-production.appspot.com/service/json/1/notifications?environment=production&group=auth0%7C5a68dc51cb30df3877a1d7c4&apiVer=1

This gives the endpoint for a notification websocket host. Haven't used it so far.

Use of this API is on your own risk. Do NOT contact the reMarkable support team if anything doesn't work as described here. This project is not affiliated with reMarkable AS, Oslo.

Clone this wiki locally