HTTP Request node → 401 with FAL API (Authorization: Key header sent)

n8n: Cloud (trial) v1.12.x
Node: HTTP Request → POST

Goal:
Call the FAL API to generate an image (Queue or Sync).

Endpoints tested:

Headers (masked):
Authorization: Key :****************
Content-Type: application/json

Body (test):
{ “prompt”: “ping” }
—or for edit—
{ “prompt”: “test”, “image_urls”: [“https://.jpg”] }

Error:
401 — “Authorization failed - please check your credentials”

What I’ve tried:

  • Authentication: None + Send Headers: ON (manual headers above)
  • Authentication: Header Auth credential (Authorization: Key <API_KEY>)
  • Created a new Server API key on fal.ai
  • Tried different public endpoints (not Partner/gated)
  • Same key works in FAL’s Playground

Question:
Is there anything in the HTTP Request node that could block or change the
Authorization: Key ... header? Do I need a specific Auth type, or is a
manual header enough? A minimal working example would be great.

Attachments (screenshots):

  1. Node Parameters
  2. OUTPUT → From HTTP Request → Request → headers (key masked)

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