Home/ Tools/ cURL to Mule
πŸ”

Postman cURL β†’ Mule HTTP Request

Copy cURL from Postman or browser DevTools and get production-ready MuleSoft HTTP Request Configuration and Processor XML instantly. All headers and query parameters are automatically extracted into dynamic DataWeave expressions.

MuleSoft HTTP Connector cURL 100% Client-Side
Config Name:
Output Mode:
Postman cURL Command
HTTP Request Configuration
HTTP Request Processor

How to Use cURL to Mule

Go from a working cURL command to production-ready MuleSoft HTTP Request XML in seconds.

1. Copy from Postman

In Postman, click the </> (Code) icon in the right sidebar. Select cURL from the dropdown and copy the snippet.

2. Choose Output Mode

Select Config + Processor for global config and request blocks, or Embedded for a standalone request using the full URL attribute.

3. Contextualize Options

Toggle Follow Redirects, Response Timeout, or Streaming Mode. All options generate valid Mule XML attributes instantly.

Copy Into Anypoint Studio

Click Copy and paste directly into your Mule project's XML config file. Headers and query params are already wired as dynamic input parameters.

Frequently Asked Questions

What cURL formats are supported?
This tool supports standard cURL commands including --header / -H, --data / -d, --request / -X, --location / -L, --user / -u, --insecure / -k, and URL with query parameters. Multi-line commands with backslash continuations are handled automatically.
Where do I find the cURL in Postman?
Open any request in Postman. On the right sidebar, click the **Code** icon (</>). Ensure **cURL** is selected in the language dropdown, and click the **Copy** icon. Paste that result directly into this tool.
What is the difference between output modes?
Config + Processor generates a global <http:request-config> and a separate <http:request> that references it. Embedded generates a single <http:request> that uses the url attribute to define the connection β€” perfect for quick transformations.
How are headers and query params generated?
Headers are added inside <http:headers> as a DataWeave map expression with each header key-value pair. Query parameters extracted from the URL are added inside <http:query-params> the same way. Both follow MuleSoft's recommended dynamic input parameter standards.
Does this tool handle authentication?
Yes. If --user / -u is detected, basic authentication config is generated. Bearer tokens and API keys in headers are preserved as-is in the headers block. For OAuth, you'll want to configure that separately in Anypoint Studio.
Is my data safe?
Your cURL commands never leave your browser. All parsing happens 100% client-side in JavaScript. No data is sent to any server. cURL commands often contain Authorization headers or API keys β€” they stay on your machine only.

From the Blog

Deeper dives into MuleSoft HTTP connector configuration and integration patterns.

Loading latest articles...

🀠 Find this tool useful?

Manually writing Mule HTTP Request XML from cURL is tedious. If this tool saved you time, a coffee is always appreciated!