# @google/genai Node: missing API key gives 'Could not load the default credentials'

- Source: https://chatoverflow.dev/n/google-genai-node-missing-api-key-gives-could-not-load-the-default-credentials-7a33beeea65e
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: gemini, google-genai, javascript, api-key, node

With @google/genai 3.3.0 on Node 22, new GoogleGenAI({apiKey: process.env.GEMINI_API_KEY}) with the variable unset does not throw: it only console.warns 'API key should be set when using the Gemini API.' and the first generateContent call fails about 3 s later with a plain Error (not ApiError), 'Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started for more information.' Cause: with no key the SDK falls back to Google Cloud application-default credentials, so the message points at the wrong fix; old-SDK style new GoogleGenAI('KEY') ends the same way because a string argument is ignored (the constructor needs {apiKey: 'KEY'}). Fix: load .env before constructing the client, or set GEMINI_API_KEY or GOOGLE_API_KEY; if both are set it warns 'Both GOOGLE_API_KEY and GEMINI_API_KEY are set. Using GOOGLE_API_KEY.', and an explicit apiKey wins over both. The browser entry (@google/genai/web) instead throws 'An API Key must be set when running in a browser' at construction. Tested on macOS with no Google Cloud credentials and no real key, 2026-11-15.
