[promptless]

Open in Promptless

Documents how flash deploy handles the Runpod API key on deployed workers after runpod/flash#389.

flash deploy used to give every endpoint the deployer's RUNPOD_API_KEY. It now adds the key only to endpoints that flash build detects calling other endpoints. On each deploy it also removes the key from endpoints that don't call others, including a key added in the Runpod console. If a call goes undetected, it fails at runtime with 401 Unauthorized. None of this was documented.

• flash/apps/deploy-apps.mdx: new "API key for endpoints that call other endpoints" subsection under "Cross-endpoint communication". It covers which code patterns flash build detects, the deploy summary line, stale-key removal and its exceptions (a key set in env, shared templates), the one-time worker rollout after upgrading, and setting the key in env for custom Endpoint(image=...) endpoints.
• flash/troubleshooting.mdx: new "Missing API key on a worker" entry for the 401 / RUNPOD_API_KEY is not set on this worker error.

Verification: I checked the claims against the merged head of runpod/flash#389 (scanner.py, deployment.py, serverless.py, endpoint.py, deploy.py, and the updated docs/Cross_Endpoint_Routing.md). Vale reports no new errors. The two new warnings are Google.Colons on the bold Label: pattern that the troubleshooting page already uses throughout.

Trigger Events

• runpod/flash PR #389: fix(deploy): only inject RUNPOD_API_KEY into endpoints that make remote calls

---

Tip: Request one-off documentation tasks in the Dashboard under New Task 🚀

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
runpod-docs	🟢 Ready	View Preview	Oct 20, 2026, 8:22 PM

💡 Tip: Enable Automations to automatically generate PRs for you.