Authorization for api/share/direct?

[2luca]

Hello, I use filebrowser quantum with my n8n workflows. I tested the api with the /swagger function and was able to create a download link for my file. Now I am trying to create a download link in my workflow and get this error message:

401 - "{"status":401,"message":"no token present in request"}"

This is the request in the http node:

{ "headers": { "accept": "application/json" }, "method": "GET", "uri": "https://data.domain.com/api/share/direct", "gzip": true, "rejectUnauthorized": true, "followRedirect": true, "resolveWithFullResponse": true, "followAllRedirects": true, "timeout": 300000, "qs": { "path": "/media/pdf_20251106_xgrwa.pdf", "source": "shared" }, "encoding": null, "json": false, "useStream": true }

I imported the curl command (which I could use to create the link) in the n8n node:

curl -X 'GET'
'https://data.domain.com/api/share/direct?path=%2Fmedia%2Ftest-n8n.pdf&source=shared'
-H 'accept: application/json'

I already created an api key. How should I implement it now? Or do I have to do it completely differently?

[2luca]

Got it.

You have to use the authorization token like this:

curl -X 'GET'
'https://data.domain.com/api/share/direct?path=%2Fmedia%2Ftest-n8n.pdf&source=shared'
-H 'accept: application/json'
-H Authorization: Bearer XxxXxxXXXXxxX"

Now it works.

[gtsteffaniak]

Good point I need to document this. All forms of authentication use JWT, theres 3 possible ways a request can be authenticated:

1. Specify token in authentication header as @2luca mentioned
2. Specify token in query https://data.domain.com/api/share/direct?path=%2Fmedia%2Ftest-n8n.pdf&source=shared&auth=<token>
3. make a request with token set in filebrowser_quantum_jwt cookie

All 3 will be accepted.