Bright Data Authentication problem while getting data with Snapshot Id

Questions
1

Describe the problem/error/question

Hello! I’m using a HTTP Get Node for getting Bright Data’s snapshot’s data and it was working well until a week ago. Today I got an error message that the Token Auth is not allowed, which is weird cuz the auth was working well for triggering Bright Data’s Scrapping…Does anyone have the same problem?

cURL is this, and the format is JSON:

curl -X GET "https://api.brightdata.com/datasets/v3/snapshot/SNAP_ID" \
  -H "Authorization: Bearer MY_TOKEN"

This is how it looks like on Node:

image
image1136×1432 63 KB

image
image1136×1230 46.1 KB

What is the error message (if any)?

401 - “Token auth is not allowed”

Please share your workflow

image
image1794×490 68.7 KB

Share the output returned by the last node

{
“errorMessage”: “Authorization failed - please check your credentials”,
“errorDescription”: “Token auth is not allowed”,
“errorDetails”: {
“rawErrorMessage”: [
“401 - "Token auth is not allowed"”
],
“httpCode”: “401”
},
“n8nDetails”: {
“nodeName”: “Fetches scraped Glassdoor data using snapshot ID”,
“nodeType”: “n8n-nodes-base.httpRequest”,
“nodeVersion”: 4.2,
“itemIndex”: 0,
“time”: “12/9/2025, 2:10:26 PM”,
“n8nVersion”: “1.122.4 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: Authorization failed - please check your credentials”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts:858:16)“,
" at processTicksAndRejections (node:internal/process/task_queues:105:5)”,
" at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1074:8)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1255:11)”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1691:27",
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_08b575bec2313d5d8a4cc75358971443/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2307:11"
]
}
}

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

First of all I would recommend to use the built-in credentials feature of n8n. You can add “Header Auth” credentials and add your values as following (YOUR_TOKEN needs to be replaced of course!):

image
image1995×1052 125 KB

And to fix your issue, I’d recommend to check the current token configuration on Bright Datas side. Can you confirm that the token is valid, has the correct expiration date (e.g. unlimited) and the permission levels align with the scope of your request?

1 Like
3

I’m getting the exact same error - everything worked fine and then suddenly I get 401. BrightData status page reports no problems, but this is very odd.

4

Are you both using n8n Cloud or selfhosted? Maybe the n8n cloud ip range got blocked by them?
In this case, I would recommend to just contact the Bright Data support immediately.

1 Like
5

Well, actually I’m just calling brightdatas apis from Python for OSINT purposes, not related to n8n at all :smiley: I just found this issue and since I have the exact same problem I thought I’d answer

6

This worked! Thanks a lot

1 Like
7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.