Converting cURL to PHP: Native cURL vs Guzzle

✓ Last tested: June 2026 · Verified against PHP 8.3+ and Guzzle 7+

1. Field Notes: The curl_setopt Nightmare

PHP is unique because its native HTTP client is literally a direct wrapper around libcurl. On the surface, this sounds like it should make converting bash cURL commands into PHP incredibly easy.

In reality, it's notoriously frustrating.

A few months ago, I was integrating a legacy PHP 8 backend with a modern GraphQL API. The API docs provided a standard cURL POST request with a nested JSON query. I initialized a PHP cURL handle and started writing out the curl_setopt lines.

I forgot exactly one constant: curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);.

Instead of capturing the API response into a variable so I could parse it, PHP dumped the raw JSON directly to the output buffer, destroying the HTML layout of the page and throwing a silent error in my parsing logic.

Translating cURL to PHP requires memorizing dozens of obscure CURLOPT_* constants. This guide breaks down exactly how to parse cURL flags into both native PHP cURL and the much preferred, modern Guzzle HTTP client.

---

2. The Anatomy of a cURL Command vs PHP Clients

When converting cURL to PHP, you have two choices:

1. Native PHP cURL: Procedural, verbose, requires no external dependencies (built into PHP).
2. Guzzle: Object-oriented, elegant, requires Composer.

The Basic Mapping

cURL Flag	Native PHP Equivalent	Guzzle Equivalent
[URL]	curl_init($url)	$client->request('GET', $url)
-X POST	CURLOPT_CUSTOMREQUEST, 'POST'	$client->post($url)
-H "Key: Val"	CURLOPT_HTTPHEADER, ['Key: Val']	['headers' => ['Key' => 'Val']]
-d '{"a":1}'	CURLOPT_POSTFIELDS, json_encode($data)	['json' => ['a' => 1]]
-u user:pass	CURLOPT_USERPWD, "user:pass"	['auth' => ['user', 'pass']]
-L	CURLOPT_FOLLOWLOCATION, true	Default in Guzzle

---

3. Step-by-Step Conversion Examples

Let's translate real-world cURL examples into both native PHP and Guzzle.

Example 1: The Simple GET Request

The cURL Command:

curl https://api.github.com/users/octocat

The Native PHP Equivalent:

<?php
$ch = curl_init('https://api.github.com/users/octocat');

// REQUIRED: Tell cURL to return the output as a string instead of dumping it directly
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
// REQUIRED for Github API: User-Agent header
curl_setopt($ch, CURLOPT_USERAGENT, 'PHP Script');

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);

The Guzzle Equivalent:

<?php
use GuzzleHttp\Client;

$client = new Client();
$response = $client->request('GET', 'https://api.github.com/users/octocat', [
    'headers' => ['User-Agent' => 'PHP Script']
]);

$data = json_decode($response->getBody(), true);

Example 2: POST Requests with JSON Payloads

The cURL Command:

curl -X POST https://api.stripe.com/v1/customers \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN_HERE" \
  -d '{"name": "Jenny Rosen", "email": "jenny@example.com"}'

The Native PHP Equivalent:

<?php
$url = "https://api.stripe.com/v1/customers";
$payload = json_encode([
    "name" => "Jenny Rosen",
    "email" => "jenny@example.com"
]);

$ch = curl_init($url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST");
curl_setopt($ch, CURLOPT_POSTFIELDS, $payload);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    "Content-Type: application/json",
    "Authorization: Bearer " . getenv('API_TOKEN'),
    "Content-Length: " . strlen($payload)
]);

$response = curl_exec($ch);
curl_close($ch);

The Guzzle Equivalent:

<?php
use GuzzleHttp\Client;

$client = new Client();

// Guzzle's 'json' option automatically sets the Content-Type header 
// and runs json_encode() for you!
$response = $client->post('https://api.stripe.com/v1/customers', [
    'headers' => [
        'Authorization' => 'Bearer ' . getenv('API_TOKEN')
    ],
    'json' => [
        'name' => 'Jenny Rosen',
        'email' => 'jenny@example.com'
    ]
]);

Notice how much cleaner Guzzle is. By passing the array to the json key, Guzzle handles the JSON serialization and header management entirely behind the scenes.

---

4. Handling Edge Cases: Form Data and Basic Auth

Legacy APIs like Twilio often use application/x-www-form-urlencoded data and Basic Authentication.

The cURL Command:

curl -X POST https://api.twilio.com/2010-04-01/Accounts/AC/Messages.json \
--data-urlencode "Body=Hello World" \
--data-urlencode "From=+15017122661" \
--data-urlencode "To=+15558675310" \
-u AC_SID:AUTH_TOKEN

The Native PHP Equivalent:

<?php
$url = "https://api.twilio.com/2010-04-01/Accounts/AC/Messages.json";
$formData = http_build_query([
    "Body" => "Hello World",
    "From" => "+15017122661",
    "To" => "+15558675310"
]);

$ch = curl_init($url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, $formData);
// Native cURL has a specific option for -u basic auth
curl_setopt($ch, CURLOPT_USERPWD, "AC_SID:AUTH_TOKEN");

$response = curl_exec($ch);
curl_close($ch);

The Guzzle Equivalent:

<?php
use GuzzleHttp\Client;

$client = new Client();

// Use the 'form_params' option for x-www-form-urlencoded data
// Use the 'auth' option for basic authentication
$response = $client->post('https://api.twilio.com/2010-04-01/Accounts/AC/Messages.json', [
    'auth' => ['AC_SID', 'AUTH_TOKEN'],
    'form_params' => [
        'Body' => 'Hello World',
        'From' => '+15017122661',
        'To' => '+15558675310'
    ]
]);

---

5. Automating the Translation Process

Memorizing the differences between CURLOPT_POST, CURLOPT_CUSTOMREQUEST, and how Guzzle handles json vs form_params is exhausting.

Instead of writing out headers by hand and risking silent output buffer dumps, you should automate the process.

Use our free cURL Command Converter to instantly translate any cURL command into production-ready PHP code. You can choose to generate native curl_setopt procedural code, or clean, modern Guzzle implementations.

---

Frequently Asked Questions

Q: How do I handle cURL -k or --insecure in PHP? A: In native PHP, set curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false). In Guzzle, pass 'verify' => false in the request options array. Never do this in production, as it opens your application to Man-in-the-Middle (MitM) attacks.

Q: What about multipart/form-data uploads via cURL -F? A: In native PHP, pass an array to CURLOPT_POSTFIELDS and use the CURLFile class for the file value: ['file' => new CURLFile('/path/to/image.jpg')]. In Guzzle, use the multipart array option.

---

External Sources

• PHP Official Documentation: cURL
• Guzzle PHP HTTP Client Documentation
• cURL Official Documentation & Manual

---

Abu Sufyan · Full-stack developer · Founder of WebToolkit Pro Github

Last updated: June 2026