SOAP Request Builder
Build a SOAP 1.2 envelope for one operation: namespace, element name and one parameter per line, with every value XML-escaped.
What the SOAP Request Builder does
The operation and each parameter name are checked as element names, because a name with a space or an angle bracket cannot be written as an element. The namespace is validated as an absolute URL and then emitted unchanged, since a namespace URI is an identifier.
The envelope uses the SOAP 1.2 namespace, http://www.w3.org/2003/05/soap-envelope. A service that expects SOAP 1.1 needs a different namespace and is not what this page emits.
This builds a request body; it does not send it and does not add WS-Security headers. A service that requires a security token or a signature needs those headers added by hand.
How to use it
Set Operation, Namespace and Parameters, or press Run with the defaults.
Read the SOAP envelope below: the Body contains the operation element with one child per parameter line.
Check a SOAP envelope value containing an ampersand — it is escaped, so the envelope stays well formed.
Worked example
Input:
Output:
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:tns="https://api.example.com">
<soap:Body>
<tns:GetUser>
<tns:id>42</tns:id>
</tns:GetUser>
</soap:Body>
</soap:Envelope>
Why it runs in your browser
The result is produced on this page with JavaScript, so it works offline after the page loads and nothing you enter is sent anywhere.
A SOAP 1.2 envelope around one operation: the namespace declared once as `tns`, the operation element, and one child per parameter.
Every value is XML-escaped, so a parameter containing `&` or `<` stays text instead of breaking the document.
What it does, and what it does not
The operation and each parameter name are checked as element names, because a name with a space or an angle bracket cannot be written as an element. The namespace is validated as an absolute URL and then emitted unchanged, since a namespace URI is an identifier.
The envelope uses the SOAP 1.2 namespace, `http://www.w3.org/2003/05/soap-envelope`. A service that expects SOAP 1.1 needs a different namespace and is not what this page emits.
This builds a request body; it does not send it and does not add WS-Security headers. A service that requires a security token or a signature needs those headers added by hand.
How to use SOAP Request Builder
Set Operation, Namespace and Parameters, or press Run with the defaults.
Read the SOAP envelope below: the Body contains the operation element with one child per parameter line.
Check a SOAP envelope value containing an ampersand — it is escaped, so the envelope stays well formed.
What to Expect
Best for
- Building a test request for a SOAP service
- Checking the envelope shape a service expects
Not ideal for
- WS-Security headers, which need a token
- Sending the request, which this page does not do
What this tool keeps
- Parameter order as you wrote it
- Escaped values
What may need cleanup
- Add a Security header when the service requires it
- A SOAP 1.1 service needs a different envelope namespace
Common errors
- The page refuses it: operation must be an element name
Example use cases
- Writing a request to paste into a SOAP client
- Checking an operation's parameter names
Sample input
Request fields:
Sample output
SOAP envelope: <?xml version="1.0" encoding="UTF-8"?> …
Who this is for
- Developers integrating a SOAP service
- Anyone testing a legacy endpoint
Frequently asked questions
Does it send the request?
No. It builds an envelope you can copy into a client. There is no network call on this page.
Is the SOAP 1.1 namespace supported?
No. The page emits SOAP 1.2. A 1.1 service needs the older namespace and a slightly different fault shape, so it is not a flag on this page.
Are values escaped?
Yes, &, <, > and the quote are escaped, so a parameter can contain any text without breaking the envelope.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.