Paste a cURL Command and Let Claude Turn It into Proper Integration Code
API documentation almost always includes cURL examples. They're great for testing in the terminal but useless in your application code. Paste the cURL command into Claude and it translates it into a proper HTTP call in whatever language you're using.
> convert this cURL to PHP using Guzzle:
>
> curl -X POST https://api.example.com/v1/charges \
> -H "Authorization: Bearer sk_test_123" \
> -H "Content-Type: application/json" \
> -d '{"amount": 2000, "currency": "usd"}'
Claude produces a typed, production-ready implementation — not just a raw HTTP call, but code with proper error handling, response parsing, and your framework's conventions:
$response = Http::withToken(config('services.example.secret'))
->post('https://api.example.com/v1/charges', [
'amount' => 2000,
'currency' => 'usd',
]);
if ($response->failed()) {
throw new PaymentException($response->json('error.message'));
}
return $response->json();
This works for any language and HTTP client:
> convert this cURL to Python using requests
> convert this cURL to JavaScript using fetch
> convert this cURL to Go using net/http
Claude handles all the cURL flags you'd otherwise need to decode manually:
-Hheaders — maps to the right header method in your HTTP client-ddata — parses JSON body and creates a proper request object-ubasic auth — converts to your client's auth mechanism-Xmethod — uses the correct HTTP verb-Fform data — handles multipart form uploads--data-urlencode— uses proper URL encoding
You can also paste an API response alongside the cURL and Claude generates typed response models:
> here's the cURL and a sample response — create the request
> and a typed response class that maps the JSON fields
cURL is for testing, not for production — paste it and let Claude write the real code.
via Claude Code
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.