SOAP Client
SOAP requests can use your browser or the server proxy
Why: Sending a SOAP envelope contacts your service. Proxy mode or a CORS fallback passes the request through this deployment.
Data sent:
- Target URL, configured headers and credentials, and the request payload
- SOAPAction, XML envelope and configured TLS certificates or keys when proxying
Data handling: Direct mode sends requests from your browser to the target. Proxy mode sends the configured request through this deployment; the target also receives it. Review credentials and payloads before sending.
Audit the source: src/app/api/proxy/route.ts
Audit the source: src/app/tools/soap-client/page.tsx
SOAP 1.1
Request
Load template
Body
Headers (0)
SSL
cURL
Response
Send a request to see the response
Quick Tips
SOAP 1.1: Uses text/xml content type and SOAPAction header
SOAP 1.2: Uses application/soap+xml content type
WS-Security: Load the security template and add credentials