Making HTTP Requests with curl

In Plain English

`curl` (Client URL) is the Swiss Army knife for transferring data over network protocols (HTTP, HTTPS, FTP, WebSocket). It supports custom headers, JSON bodies, authentication tokens, cookies, form uploads, and silent scripting output.

The Mental Model

"`curl` is like a headless web browser: instead of rendering graphics and CSS, it directly speaks the raw HTTP language to send requests and inspect headers and responses."

Deep Dive: How It Works

Essential Flags: `-s` (silent / no progress bar), `-S` (show error if it fails), `-L` (follow HTTP redirects), `-I` (fetch headers only), `-X <METHOD>` (HTTP verb like POST/PUT/DELETE), `-H <HEADER>` (custom header), `-d <DATA>` (request payload).

Formatting Status Codes: `curl -s -o /dev/null -w "%{http_code}" URL` extracts only the numeric HTTP response status code (e.g. 200, 404).

JSON API Pattern: `curl -s -H "Content-Type: application/json" -d '{"key":"value"}' URL`.

Syntax Blueprint

curl -s https://api.example.com/data
curl -I https://zencompiler.com            # Headers only
curl -s -X POST -H "Content-Type: application/json" -d '{"query":"bash"}' URL
STATUS=$(curl -s -o /dev/null -w "%{http_code}" URL)

Use curl -s for clean scripting and -w "%{http_code}" for HTTP health checks.

Core Rules to Remember

Silent Scripting: Always combine -s with -S (`curl -sS`) to hide progress bars while preserving error messages.

Follow Redirects with -L: Crucial for modern HTTPS sites that redirect from http:// or trailing slashes.

Status Code Extraction: Extract 200, 301, 401, 500 directly into bash variables for health checks.

Common Beginner Traps & How to Fix Them

Mistake:Running curl without `-L` on a URL that redirects, receiving an empty 301 Moved Permanently.

Why it happens: curl does not follow 301/302 redirects automatically.

How to fix: Include `-L` (`curl -sSL`) to follow redirection chains.

Pro Tip: Use `curl -s URL | jq .` to automatically format, colorize, and parse JSON API responses in terminal.

Live Interactive Example

Hit Run Code to see it live

Sending HTTP Requests and Parsing Status Codes

Git 2.45 / CLI

Output Console

Click "Run Code" to view the rendered output.

How it works: curl -w "%{http_code}" extracted the status code without printing response body.

Your Turn: Micro Challenge

No pressure! Edit the starter code below and test your solution with instant feedback.

Micro Exercise

Simulate HTTP Status Check

Echo "HTTP Status: 200 OK" to simulate a successful curl response.

Sandbox Output

Click "Run & Check" to test your solution.

Finished reading and practicing?

Mark this lesson as completed to update your course progress.