cURL with Bearer token in Node.js

Paste a curl command that uses Bearer token and get Node.js code using native fetch. Toolpaper also detects secrets and offers a one-click redaction before sharing.

Quick answer

To convert a cURL command to Node.js, paste it into the Toolpaper workbench below. It parses the command in your browser and emits idiomatic Node.js code — headers, query string, request body, authentication (Bearer, Basic, API key), and cookies are all wired up automatically. No data is uploaded; conversion is fully client-side.

Prefer a different target? See the full cURL to Node.js reference, or jump to the same guide in JavaScript, Python, or Go.

InputcURL command
1 secret
MethodGET·Headers1·Body—· Chars 73
OutputJavaScript · Node fetch(Node 18+)
// Node 18+ has global fetch
const response = await fetch("https://api.example.com/me", {
  method: "GET",
  headers: {
    "Authorization": "Bearer YOUR_TOKEN"
  },
  redirect: "manual"
});
const data = await response.json();
Inspect

Example

A representative curl command for this scenario. Paste your own above to convert an exact match.

curl input
curl https://api.example.com/me \
  -H "Authorization: Bearer YOUR_TOKEN"

Implementation notes

  • Authorization: Bearer <token> is preserved verbatim so JWT signatures stay intact — no re-encoding, no whitespace normalization.
  • Secrets are visible in the parsed request. Use the Clean panel's redact-and-diff flow before you paste the command anywhere.
  • Shareable links Base64-encode the input — they never leave your browser, and cleaned versions produce different links.

Common mistakes

  • Pasting a Bearer token straight into a public repo — the Clean panel flags common JWT and opaque-token shapes.
  • Not rotating a leaked credential because "it's only in a screenshot" — screenshots get OCR'd, redact first.
  • Trusting HTTPS alone for API keys in query strings — proxies log URLs. Prefer headers, which the converter defaults to.

Common questions

How is Bearer token rendered in Node.js?
The Authorization: Bearer header passes through to the generated request as-is. Use Toolpaper's Clean panel to redact the token before sharing.
Can I redact the secret before sharing?
Yes. Open the Clean panel — Toolpaper detects Bearer tokens, Basic credentials, and common API-key patterns and replaces them with <REDACTED> in a diffable view.
Does anything leave my browser?
No. Parsing, redaction, and generation are 100% client-side.

More auth flows in Node.js

Node.js hub →

The same guide in other languages

All guides →

Full Node.js reference on the cURL to Node.js hub, or open the main converter for all 18 targets.