400 Error, when trying to mint user token

[delize]

: ~
$ docker run -it --rm -v ./rmapi-ci-config:/app/.config/rmapi \                                                                                                                                                                           [18:55:02]
    rmapi auth
[2026-05-30 16:55:13] Starting rmapi authentication...
[2026-05-30 16:55:13] Visit https://my.remarkable.com/device/browser/connect to get a one-time code
Enter one-time code (go to https://my.remarkable.com/device/browser/connect):
ERROR: 2026/05/30 16:55:24 auth.go:53: failed to create user token from device token request failed with status 400

This is my binary tool, but it uses the .34 version of the binary that was released last week.

When trying to auth from a fresh brand new account with no devices attached, I get this error. I assume the fault here is that there is no device attached to the account, but, wanted to see if there was any way to do this - so I could build a CI/CD system using the rmapi not on my personal account.

1. As a way to validate when something randomly breaks with the API response
2. As a way to test something I am trying to build

Any thoughts?

EDIT:
It seems like that the rmapi also drops the error message pertaining to this being the exact cause from the API Response unless turning on TRACE.

$ docker run -it --rm -e RMAPI_TRACE=1 \                                                                                                                                                                                                  [18:55:24]
    -v ~/rmapi-ci-config:/app/.config/rmapi \
    --entrypoint rmapi container_image:latest ls /
Trace: 2026/05/30 17:15:11 transport.go:241: ---- start request ----
Trace: 2026/05/30 17:15:11 transport.go:249: request: POST /token/json/2/user/new HTTP/1.1
Host: webapp-prod.cloud.remarkable.engineering
Authorization: Bearercontent-type: application/octet-stream
user-agent: rmapi
x-goog-hash: crc32c=AAAAAA==

 <nil>
Trace: 2026/05/30 17:15:11 transport.go:265: HTTP/2.0 400 Bad Request
Content-Length: 76
Alt-Svc: h3=":443"; ma=2592000
Content-Type: text/plain; charset=utf-8
Date: Sat, 30 May 2026 17:15:11 GMT
Server: Google Frontend
Via: 1.1 google
X-Cloud-Trace-Context:
X-Content-Type-Options: nosniff
X-Ratelimit-Limit: 5
X-Ratelimit-Remaining: 4
X-Ratelimit-Reset: 12

You must connect a rM device in the webapp before you can use this service.
 <nil>
Trace: 2026/05/30 17:15:11 transport.go:272: request failed with status 400
ERROR: 2026/05/30 17:15:11 auth.go:53: failed to create user token from device token request failed with status 400
FAIL

I believe that:

You must connect a rM device in the webapp before you can use this service.

Should be shown in the output, not hidden.

[Azeirah]

Ah, this is new! Previously you could connect to the service without a connected device. There were some changes recently to the reMarkable infra, see #62.

I believe that:

You must connect a rM device in the webapp before you can use this service.

Should be shown in the output, not hidden.

I agree.