Paperless-ngx "The token does not have permission to access the API."

[zweckj]

The problem

Getting the The token does not have permission to access the API. error since a while. In the earlier betas everything was working correctly.
The token is of my (sole) admin account on the system. Nothing else in the logs.

What version of Home Assistant Core has the issue?

core-2025.6.0

What was the last working version of Home Assistant Core?

core-2025.6.0b0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

paperless_ngx

Link to integration documentation on our website

https://www.home-assistant.io/integrations/paperless_ngx/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @fvgarrel, mind taking a look at this issue as it has been labeled with an integration (paperless_ngx) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of paperless_ngx can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign paperless_ngx Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

paperless_ngx documentation
paperless_ngx source
_{^{(message by IssueLinks)}}

[fvgarrel]

That sounds strange. You only updated Home Assistant to the stable version, and since then it hasn't worked anymore? Everything else in Paperless has stayed the same?

Which version of paperless are you running, so I can try to reproduce it.

[zweckj]

Exactly. 2.16.3

[fvgarrel]

I’ve tried many things but unfortunately haven’t been able to reproduce the behavior. Neither updating from the beta b0 to the 06 version, nor using Paperless users with little to no permissions caused any issues. I also tested various infrastructure setups (with proxy / without proxy / SSL / no SSL / self-signed cert, DNS host / IP host), but couldn’t find any errors. The statistics should always work, and the integration should be configurable.

So I have a few questions:
When you log in with that user, are you able to access both the /api/ and /api/statistics endpoints with your browser?
Does the user have admin rights or superuser rights? Unfortunately, that’s a difference that matters for the API, but should not stop the Integration from setup.

Are there any helpful logs in Paperless (paperless.log)?

Is it possible that you have a proxy in between that’s returning a 403 error code?

[zweckj]

If I'm alone with that it’s gotta be something on my end. I assume it’ll be probably something stupid like the proxy/some firewall - should've thought of that first 🙈. Thanks for checking.

[Futo8681]

I've experiencing the same problem. Also running paperless 2.16.3 and homeassistant core-2025.6.1 (but on docker).

I've tested the API Token in the Swagger UI of my Paperless Instance at https://mypaperlessdomain.de/api/schema/view/#. There I can authorize via tokenAuth. I've tried to get document types there, that also works as aspected.

The paperless user I've created the token for is the only one and is also Super Admin. I've already tried to regenerate a new token, without any change.

[zweckj]

I figured it out, in my case it wasn't the integration's fault but DNS's (of course), where my HA was suddenly trying to reach my paperless from the internet and was getting blocked by the proxy.

[Futo8681]

Seems to be the same on my end...
I'm using a lokal DNS to route a domain directly to the paperless server (which also is the HA Sever, its a Synology)... Seems like the integration bypasses my lokal DNS somehow and tries to reach paperless from outside my network, although the DNS is configured network-wide...