⌘ K
curl → ps1 · Invoke-RestMethod · headers · body · live

Convert cURL to PowerShell

Translate a cURL command into Invoke-RestMethod or Invoke-WebRequest — Windows-friendly, ready to drop into a .ps1 script.

cURL → PowerShell
Input
161 B
4 lines
Output
231 B
2 lines
Status
ready
live
Ratio
1.43×
out/in
input · curl command
output · powershell
$response = Invoke-RestMethod -Uri "https://api.example.com/users" -Method POST -Headers @{ "Content-Type" = "application/json"; "Authorization" = "Bearer abc123" } -Body '{"name":"Alice","role":"admin"}'
$response | ConvertTo-Json
Quick Start

How to port cURL to PowerShell

PowerShell's Invoke-RestMethod is the idiomatic way to call HTTP APIs on Windows. The generator emits a hashtable for headers and uses splatting for clean parameter passing.

  1. 01

    Paste cURL

    From DevTools, Postman, an SDK doc — anything that emits a cURL command.

    Parsing is strict-but-tolerant — comments and trailing commas are accepted on input where the source format historically permits them; output stays canonical.

    inputstricttolerantliveparse
    in · sourcecurl · live
    curl -X POST https://api.example.com
    loaded · parsedtarget · ready
  2. 02

    Parser pulls fields

    URL, method, headers, body and basic auth are extracted into a structured shape.

    Conversion preserves type information where the target supports it (numbers stay numeric, booleans stay boolean) so the destination parser never has to re-coerce.

    parsetype-preservinglosslesslivememoised
    url · optionsheaders · live
    { url, method, headers, data }
    options applied · liveround-trip
  3. 03

    Emit PowerShell

    The generator turns the parsed command into idiomatic code for the target stack.

    Re-encoding is idempotent: running output back through the same converter produces the same bytes, which keeps round-trips git-friendly.

    genidempotentround-tripdiff-cleandeterministic
    out · convertedPowerShell · ready
    $res = Invoke-RestMethod -Uri $url -Method $method -Headers $h
    converted · livediff-clean
  4. 04

    Copy or download

    Drop into your project and tweak as needed.

    Copy writes via navigator.clipboard.writeText; downloads use the target’s native MIME so editors apply the right syntax highlighting on open.

    exportclipboardtarget MIMEblobclient-side
    ✓ · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Converting between formats, safely

Pick the strictest source format

Lossy formats hide bugs. Choose JSON or YAML as your source-of-truth, convert downstream as needed.

Round-trip in CI

If your converter is idempotent, your CI can verify A → B → A equals the original. Catches subtle data loss.

Numbers vs strings differ

YAML/TOML have a number type; CSV doesn’t. Quote IDs in CSV to keep leading-zero values intact.

Watch character encoding

Source format may be Latin-1 / Windows-1252; target should be UTF-8. Convert encoding before structure.

Preserve comments where you can

YAML and TOML support comments. Don’t silently drop them — they often encode intent.

Schema-aware beats blind

Use a schema to guide conversion. Field types, required-ness, and defaults survive better with structure.

Related toolscURL to fetch()cURL to C#cURL to PythoncURL to GocURL to RubycURL to Code
Use Cases

When to port cURL to PowerShell

Migration, polyglot teams, integration tests.

Windows automation

Drop into scheduled tasks or DSC configs. Type information survives: numbers stay numeric, booleans stay boolean, strings stay strings. The destination parser doesn't have to re-coerce, which avoids the "'true' becomes "true"" bug class.

round-trip safe

Azure / AWS scripts

Use in provisioning and ops scripts. Run output back through the inverse converter to verify idempotent round-trips in CI. A → B → A should produce byte-identical input — if it doesn't, you've found data loss.

type-preserving

DevOps pipelines

Embed in Azure DevOps / GitHub Actions PowerShell steps. Comments and metadata survive where the target format supports them (YAML, TOML, HCL). The tool doesn't silently drop intent-encoded annotations, which keeps your config self-documenting.

schema-aware

Quick CLI

One-liner replacement for ad-hoc curl tests. Pair with a schema (JSON Schema, OpenAPI, Zod, Pydantic) to catch shape drift on either side. Catch breaking changes at conversion time rather than at runtime in production.

lossless

Onboarding

Hand-off curl examples to ops/Windows teams. Output respects target-format conventions: quoting in CSV, indent in YAML, brackets in JSON. Existing parsers don't need patches, and the result drops into legacy pipelines unchanged.

diff-clean

Cross-platform

Works on PowerShell 7+ for Linux/macOS too. Encoding-aware: handles UTF-8 vs UTF-16 vs Latin-1 / Windows-1252 transparently. The character-set surprise that breaks "works on my machine" doesn't apply here.

spec-grade
FAQ

Frequently asked questions

RestMethod auto-parses JSON. WebRequest returns the raw response — use it when you need headers/status.
Body is passed via -Body. For JSON, the parser wraps with ConvertTo-Json automatically when isJson is detected.
Headers including Authorization are passed via the -Headers hashtable.
Use -SkipCertificateCheck (PowerShell 7+) for self-signed certs in dev.
No. Parsing and code generation run locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!