Paste a cURL command → get MuleSoft HTTP Request Configuration and Processor XML instantly. Headers and query params are generated as dynamic input parameters per MuleSoft standards.
Go from a working cURL command to production-ready MuleSoft HTTP Request XML in seconds.
Copy a cURL command from your terminal, Postman, browser DevTools, or any API documentation. Paste it into the left panel.
Select Both for config + processor, Separated for just those two blocks, or Embedded to inline all values in a single processor element.
Enable TLS context for HTTPS, set response timeouts, toggle follow-redirects, or enable streaming mode. All options generate valid Mule XML attributes.
Click Copy and paste directly into your Mule project's XML config file. Headers and query params are already wired as dynamic input parameters.
--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.
<http:request-config>
element and a separate <http:request> processor referencing it via
config-ref.
Embedded generates a single <http:request> element with
host, port, and protocol inlined — useful for quick prototyping.
<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.--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.Authorization headers or API keys — they stay on your machine only.
Deeper dives into MuleSoft HTTP connector configuration and integration patterns.
Loading latest articles...