cURL to Guzzle Converter – curl to PHP Guzzle Requests

How to use the cURL to PHP Guzzle Converter

Paste your curl command into the input panel.

The Guzzle code is generated automatically; click Convert after edits.

Install Guzzle with composer require guzzlehttp/guzzle if your project does not have it.

Copy the code into your script or service class and run it.

Convert curl to Guzzle request options

This curl to Guzzle converter translates a curl command into PHP code for GuzzleHttp\Client. Rather than dumping everything into a raw body, it picks the Guzzle request option that matches your data: json for JSON payloads, form_params for URL-encoded forms, multipart for file uploads and query for the query string. The result is shorter and easier to maintain than the equivalent curl_setopt code.

Example: form post

curl -d 'name=Ann&age=31' https://api.example.com/login becomes:

$client = new Client([
    'allow_redirects' => false,
]);

$response = $client->request('POST', 'https://api.example.com/login', [
    'form_params' => [
        'name' => 'Ann',
        'age' => '31',
    ],
]);

Because the command used a bare -d with key=value pairs, the body is decoded into a form_params array. Guzzle re-encodes it and sets the application/x-www-form-urlencoded header for you.

Option mapping

JSON: a JSON body with a JSON Content-Type turns into a PHP array under 'json'; the duplicate Content-Type header is dropped.
Query string: parameters in the URL move to 'query', and the URL is shortened to its path. When a key repeats (?tag=a&tag=b), the full URL is kept instead.
Uploads: each -F field becomes a multipart entry, with files opened by fopen($path, 'r'); -T file becomes a PUT with 'body' => fopen('file', 'r').
Auth: -u user:pass maps to 'auth' => [user, pass].
Client options: -m sets 'timeout', --connect-timeout sets 'connect_timeout', -k sets 'verify' => false, and a missing -L adds 'allow_redirects' => false, because Guzzle follows redirects by default.
Compression: --compressed adds 'decode_content' => true and an Accept-Encoding: gzip, deflate header.

Limitations

Any other body, such as XML or text, is passed through as 'body'. Proxy flags (-x) and other unsupported options like --cert are not converted; each one appears as a comment right after the <?php tag. Guzzle also throws a ClientException or ServerException for 4xx and 5xx responses by default; set 'http_errors' => false if you want to inspect them like curl does.

Headers are written as an associative array, so you can merge them with defaults set on the client through the 'headers' constructor option, which is handy when many requests share one bearer token.

Working in Laravel? The Http facade wraps Guzzle, so the same options apply, for example Http::withBasicAuth() or Http::asForm()->post().

Privacy

The conversion runs in your browser, and tokens or passwords in the command are never uploaded. If you would rather use the native cURL extension, try curl to PHP. You can also test the endpoint first in the API tester.

Frequently asked questions

Which Guzzle version does the code target?

The output uses $client->request() with request options, which works in Guzzle 6 and 7. Guzzle 7 is the version installed by default with Composer on current PHP releases.

How do I use this in Laravel?

You can run the Guzzle code as is, since Laravel includes Guzzle. Or rewrite it with the Http facade, for example Http::withToken($token)->post($url, $data), which sends JSON by default.

Why does Guzzle throw an exception on a 404 response?

Guzzle's http_errors option is on by default, so 4xx and 5xx responses raise exceptions. Catch GuzzleHttp\Exception\RequestException, or pass 'http_errors' => false to handle the status code yourself.

How do I decode the JSON response?

Call json_decode((string) $response->getBody(), true) to get an associative array. Casting the body to a string reads the whole stream.

When does the converter use form_params instead of body?

It uses form_params when the data is simple key=value pairs sent without an explicit Content-Type, which is how curl's -d behaves. JSON, XML or data with a custom Content-Type stays in json or body.

cURL to PHP Guzzle Converter