Toolpaper

cURL with API key in Ruby

Paste a curl command that uses API key and get Ruby code using net/http. Toolpaper also detects secrets and offers a one-click redaction before sharing.

Quick answer

To convert a cURL command to Ruby, paste it into the Toolpaper workbench below. It parses the command in your browser and emits idiomatic Ruby 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 Ruby reference, or jump to the same guide in JavaScript, Node.js, or Python.

InputcURL command
1 secret
MethodGET·Headers1·Body—· Chars 60
OutputRuby · net/http(stdlib)
require 'net/http'
require 'uri'
require 'json'

uri = URI("https://api.example.com/me")
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = uri.scheme == 'https'

request = Net::HTTP::Get.new(uri.request_uri)
request["X-API-Key"] = "YOUR_KEY"

response = http.request(request)
puts response.body
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 "X-API-Key: YOUR_KEY"

Implementation notes

  • The X-API-Key (or custom key header) name is preserved exactly as sent; case-sensitive gateways keep working.
  • 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

  • Duplicating the key header (once via -H, once via a gateway middleware) — the generator warns when the same header appears twice.
  • 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 API key rendered in Ruby?
The X-API-Key header (or any custom API-key header name) passes through unchanged to the generated code.
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 Ruby

Ruby hub →

Bearer token in Ruby

/how-to/curl-bearer-auth-in-ruby

Basic auth in Ruby

/how-to/curl-basic-auth-in-ruby

The same guide in other languages

All guides →

In JavaScript

/how-to/curl-api-key-auth-in-javascript

In Node.js

/how-to/curl-api-key-auth-in-node

In Python

/how-to/curl-api-key-auth-in-python

In Go

/how-to/curl-api-key-auth-in-go

In PHP

/how-to/curl-api-key-auth-in-php

In Rust

/how-to/curl-api-key-auth-in-rust

In Java

/how-to/curl-api-key-auth-in-java

In Kotlin

/how-to/curl-api-key-auth-in-kotlin

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