Alexander
05/15/2026, 11:33 PMAI Evy
05/15/2026, 11:33 PMAI Evy
05/15/2026, 11:33 PMAI Evy
05/15/2026, 11:33 PMAI Evy
05/15/2026, 11:33 PMAI Evy
05/15/2026, 11:40 PMAlexander
05/15/2026, 11:40 PMAI Evy
05/15/2026, 11:40 PMAI Evy
05/15/2026, 11:40 PMAI Evy
05/15/2026, 11:40 PMAuthorization: Bearer YOUR_API_KEY .
If you're still experiencing issues:
- Double-check that you copied the complete API key from the Retell AI dashboard [(6) ]()
- Ensure the API key hasn't been deleted in the Retell AI "API Keys" section
- Try creating a new API key and updating your N8N credentials
- Verify that N8N is set to use "Bearer" (uppercase "B") as the authentication scheme [(7) ]()Alexander
05/15/2026, 11:45 PMAI Evy
05/15/2026, 11:45 PMAI Evy
05/15/2026, 11:45 PMAuthorization: Bearer YOUR_API_KEY
The word "Bearer" must come first, followed by a space, then your actual API key .
*Step 3: Configure N8N (General Guidance) *
In N8N:
1. Find where you add credentials for Retell AI
2. Look for an authentication type dropdown - select "Bearer Token" or "Header Auth"
3. In the token/key field, paste ONLY your API key (the long string)
4. Do NOT type "Bearer" yourself - N8N should add this automatically
5. Make sure there are no extra spaces before or after your key
6. Save the credential
Common Mistakes to Avoid:
- Don't include "Bearer " when pasting your key into N8N
- Don't add quotes around your API key
- Make sure you copied the complete key with no missing characters
- Verify the key hasn't been deleted in Retell AI's dashboard
If it still doesn't work, try creating a brand new API key in Retell AI and use that fresh key in N8N.AI Evy
05/15/2026, 11:45 PMAI Evy
05/15/2026, 11:45 PMAlexander
05/15/2026, 11:58 PMAlexander
05/16/2026, 12:12 AMAI Evy
05/16/2026, 12:12 AMAI Evy
05/16/2026, 12:12 AMAuthorization: Bearer YOUR_API_KEY [(1) ]() [(2) ]() [(3) ]()
- Ensure N8N is sending this as a header, not as part of the request body
- Verify there's exactly one space between "Bearer" and your API key
Alternative approach mentioned in community discussions:
If N8N's built-in authentication isn't working, you may need to use an HTTP Request node and manually configure the headers [(4) ]() [(5) ]() . Some users have reported needing to use HTTP requests instead of pre-built integrations when authentication issues persist [(4) ]() .
Verify your API key is active:
- Confirm the key hasn't been deleted from your Retell AI dashboard
- Try generating a completely new API key
- Make sure you're copying the entire key without any trailing spaces
Since the available sources don't contain specific N8N configuration details, I'd recommend:
Check out these potentially useful sources:
- [Delete Knowledge Base]()
- [Delete Agent]()
Would you like me to try to answer more generally based on my knowledge of API authentication, or would you prefer to reachAI Evy
05/16/2026, 12:12 AMAI Evy
05/16/2026, 12:13 AMAI Evy
05/16/2026, 12:13 AMAlexander
05/16/2026, 12:13 AMAI Evy
05/16/2026, 12:13 AMAI Evy
05/16/2026, 12:13 AMAuthorization
- **Value**: Bearer YOUR_API_KEY (replace YOUR_API_KEY with your actual key)
5. **Body**: Your phone call parameters (agent_id, from_number, etc.)
The authentication header format must be: Authorization: Bearer YOUR_API_KEY
Step-by-step for N8N:
- Find the "Headers" section in your HTTP Request node
- Click "Add Header" or similar button
- Enter "Authorization" as the header name
- Enter "Bearer " followed by your API key as the value (one space between Bearer and your key)
- Keep your request body with your phone call parameters
- The header and body are separate - both are needed
The API key goes in the header, while your call parameters (like agent_id, phone numbers) go in the body. You need both.AI Evy
05/16/2026, 12:13 AMAI Evy
05/16/2026, 12:13 AMAI Evy
05/16/2026, 12:19 AMAI Evy
05/16/2026, 12:19 AMAI Evy
05/16/2026, 12:19 AMAuthorization (capital A, no typos) [(1) ]()
2. **Header value must be exactly**: Bearer YOUR_ACTUAL_API_KEY
- The word "Bearer" must have a capital "B" [(2) ]()
- There must be exactly ONE space after "Bearer"
- Then your complete API key with no extra spaces
Common mistakes causing this exact error:
- Using lowercase "bearer" instead of "Bearer" (case matters for the value)
- Missing the space between "Bearer" and your API key
- Extra spaces before or after
- Not including "Bearer" at all
- Including quotes around the value
In N8N, it should look like this:
Headers section:
- Name: Authorization
- Value: Bearer sk_abc123... (your actual key, starting right after the space)
NOT like this:
- ❌ bearer YOUR_KEY (lowercase b)
- ❌ BearerYOUR_KEY (no space)
- ❌ Bearer YOUR_KEY (two spaces)
- ❌ "Bearer YOUR_KEY" (quotes included)
- ❌ Just YOUR_KEY (missing Bearer)
Make sure you're typing "Bearer" with a capital B, followed by exactly one space, then paste your API key.AI Evy
05/16/2026, 12:19 AMAlexander
05/16/2026, 12:27 AMAI Evy
05/16/2026, 12:27 AMAI Evy
05/16/2026, 12:27 AMAI Evy
05/16/2026, 12:27 AMsk_ or similar, not key_. The key you're using (key_6000d00b0c4989925f0ab4d0ad53) appears incomplete or may not be a valid Retell AI API key.
Here's what to do:
1. Go back to your Retell AI dashboard
2. Navigate to Settings → API Keys
3. Create a brand new API key (click "Add")
4. Copy the COMPLETE key - it should be much longer than what you have
5. The key will likely start with sk_ or another prefix
6. Use that complete key in N8N
In N8N, your header should look like:
- Name: Authorization
- Value: Bearer sk_abc123def456... (your full key, which will be much longer)
The authorization header format requires "Bearer YOUR_API_KEY" [(1) ]() [(2) ]() [(3) ]() [(4) ]() , and your current key appears to be either truncated or not a valid Retell AI API key.
Make absolutely sure:
- You're copying the entire key from the Retell AI dashboard
- The key hasn't been deleted or deactivated
- You're using a key specifically created for API access
Try with a fresh, complete API key and the error should resolve.AI Evy
05/16/2026, 12:27 AMAI Evy
05/16/2026, 12:30 AMAlexander
05/16/2026, 12:30 AMAI Evy
05/16/2026, 12:30 AMAuthorization
- Value: Bearer key_6000d00b0c4989925f0ab4d0ad53
Since you're still getting the 401 error with the correct format, here are the remaining possibilities:
1. Verify the header is actually being sent:
- In N8N, make sure the header is in the "Headers" section, not anywhere else
- Some N8N nodes have separate "Authentication" and "Headers" sections - use Headers
- Ensure the header isn't being overridden by credential settings
2. Check if the key is active:
- In Retell AI dashboard, confirm this specific key shows as active
- Try deleting this key and creating a completely new one
- Use the new key immediately after creation
3. Test the key directly:
You can verify the key works by testing it with a simple curl command (if you have access to a terminal) :
bash
curl --request POST \
--url <https://api.retellai.com/v3/list-chats> \
--header 'Authorization: Bearer key_6000d00b0c4989925f0ab4d0ad53' \
--header 'Content-Type: application/json'
[(2) ]()
If this curl command works but N8N doesn't, the issue is with how N8N is sending the header, not with your key or format.
4. N8N-specific check:
- Ensure you're using an HTTP Request node, not a pre-configured Retell AI node
- Disable any credential-based authentication in the node settings
- Manually add the Authorization header as shown above
If none of this works, the issue may be specific to N8N's configuration that I cannot diagnose from the available Retell AI documentation.AI Evy
05/16/2026, 12:30 AMAI Evy
05/16/2026, 12:31 AM