Skip to main content
HighContentOWASP A02:2021CWE-598

How to fix: API Key in URL Parameter

API key found in URL parameter.

Why it matters

Key leaked in referrer, history, logs.

API keys in URLs are exposed in many places.

How to fix it

  1. 1Pass API keys in headers instead of URLs.

Code examples

Move API keys out of URLs into request headers

TypeScript
// BAD: API key in URL, logged by servers, proxies, and browser history
// fetch("https://api.example.com/data?api_key=abc123")

// GOOD: API key in Authorization or X-API-Key header
fetch("https://api.example.com/data", {
  headers: {
    "X-API-Key": process.env.API_KEY!,
    // or
    Authorization: `Bearer ${process.env.API_KEY}`,
  },
});

References

Detected automatically by VulnRadar. The check id is api-key-in-url, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is API Key in URL Parameter?
VulnRadar rates this high severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id api-key-in-url, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does API Key in URL Parameter map to?
It maps to CWE-598. In the OWASP Top 10 it falls under A02:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for api key in url parameter

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: API Key in URL Parameter | VulnRadar