fal client 1.11.0 and server proxy 1.3.0: key sent only to fal, proxy refuses http and drops CORS headers
fal's JS client now sends your key only to fal hosts; the server proxy 1.3.0 is HTTPS-only and stops passing CORS headers through.
Your keys
0 of 1 ready
Create each key on its own page, paste it below, then copy the finished lines into your project's .env file. What you paste stays in this tab. It is never sent to Wirestack or saved.
- fal API keyFAL_KEYGet key
Click Create Key, pick the API preset, then copy it right away. It is only shown once
What changed
November 14, 2026: fal released @fal-ai/client 1.11.0 and @fal-ai/server-proxy 1.3.0. Both tighten where requests go and what is passed back. Most apps upgrade with no change, but a few proxy setups will break.
Client 1.11.0
- Your key stays on fal: the
Authorizationheader is only added when the request goes tofal.runorfal.ai(or a subdomain of them).fal.stream(..., { url })with a URL on any other host still sends the request, but without your key. If something relied on the key reaching a non-fal URL, it now has to set its own header. Requests routed through a proxy keep their header as before. subdomainis checked: the option may only contain letters, digits, hyphens and dots. Anything else, including a non-string value, throwsInvalid subdomain.- Streaming status: in
subscribeToStatuswithmode: "streaming", atimeoutnow rejects the returned promise (it used to throw where you could not catch it), andabortSignalnow stops the subscription. Aborting stops watching; it does not cancel the request on fal's side.
Server proxy 1.3.0
- HTTPS targets only: the target URL must be
https:, with no user info and no encoded slashes (%2f,%5c). Anything else gets a400. There is no exception forhttp://localhosttargets. allowedEndpointscovers every method:GET,PUT,PATCHandDELETEto endpoints outside the list are now refused, not onlyPOST. Queue routes (/requests/<id>,/status,/cancel) are allowed when a pattern covers their app, sofal-ai/flux/devstill allowsfal-ai/flux/requests/<id>/status. A pattern with a brace group containing a slash ({a/b,c/d}/**) will not match queue routes.- Fewer headers passed back: only
content-type, and come through from fal, with and added. headers no longer pass through, so a cross-origin setup needs its own CORS settings on the proxy route.
