stuntman / providers / soap

SOAP

Give Stuntman the provider's WSDL and it answers like the SOAP endpoint: operations, XSD checks, faults, WS-Security and XML signatures.

Stands in for

  • SOAP 1.1 and 1.2 services (WSDL 1.1)
  • WS-Security UsernameToken
  • XML signatures (XMLDSig)
  • ICP-Brasil style e-CNPJ and e-CPF certificates
  • mTLS gateways
  • Fiscal web services such as NF-e events

Everything SOAP gives you

  1. 01

    Service from a WSDL

    A URL, a file or the text: one operation per WSDL operation, a default answer from the response type, each declared fault as a named answer.

  2. 02

    Picks the operation

    By SOAPAction (1.1 header or 1.2 action), or by the element in soap:Body. Unknown operations go to Unmatched with the envelope.

  3. 03

    Checks bodies against XSD

    Missing fields, wrong types and unknown elements get the provider's Sender fault naming the field.

  4. 04

    Faults are answers

    A fault has a code (Sender or Receiver), a reason template and a detail element. It goes out with HTTP 500, as real stacks send it.

  5. 05

    WS-Security

    UsernameToken present (any) or with matching user and password; a wrong one gets the security-token fault.

  6. 06

    XML signatures

    Checks each enveloped ds:Signature (RSA-SHA1 or SHA256, C14N) and signs an element of the answers with the service's own e-CNPJ.

  7. 07

    mTLS with a CNPJ

    On :8443 the app's certificate must be signed by the Test CA, valid and carry a CNPJ; steps read it as client_cnpj.

  8. 08

    Callbacks as SOAP

    send steps post an envelope with the callback's SOAPAction; send_callback calls the app's endpoint on demand.

  9. 09

    Re-import keeps your work

    A new WSDL adds operations with default answers; your steps, answers, data and security stay.

The screens

Each number is a control or a reading on the real screen. Everything you can click there, your agent can do with a tool.

Operations from the WSDL, with their steps

Operations from the WSDL, with their steps: the SOAP screen in Stuntman
1One per WSDL operation

Each with its SOAPAction and calls today; the request and response types come from the WSDL.

1 of 5
2Receive

The envelope is checked against the WSDL's XSD and the WS-Security UsernameToken.

2 of 5
3Decide

First match wins: a cargo value over the limit gets the coverage_exceeded fault.

3 of 5
4Re-import WSDL

Reads a new WSDL and keeps your steps; the served WSDL is one click away.

4 of 5
5Operation it lacks

A call for an operation the WSDL does not have gets a Sender fault and shows in Unmatched.

5 of 5
  1. One per WSDL operation

    Each with its SOAPAction and calls today; the request and response types come from the WSDL.

  2. Receive

    The envelope is checked against the WSDL's XSD and the WS-Security UsernameToken.

  3. Decide

    First match wins: a cargo value over the limit gets the coverage_exceeded fault.

  4. Re-import WSDL

    Reads a new WSDL and keeps your steps; the served WSDL is one click away.

  5. Operation it lacks

    A call for an operation the WSDL does not have gets a Sender fault and shows in Unmatched.

A fault is a named answer

A fault is a named answer: the SOAP screen in Stuntman
1Faults from the WSDL

Declared faults arrive as answers, next to each operation's default response.

1 of 5
2Response or Fault

The same answer editor; Fault adds code, reason and detail.

2 of 5
3Code and status

Sender or Receiver (Client and Server for SOAP 1.1), sent with HTTP 500 unless you set another.

3 of 5
4Detail from the XSD

The fault's detail element is a template, checked against the WSDL's fault type.

4 of 5
5What the app gets

The whole envelope in the call's SOAP version, filled from the last call.

5 of 5
  1. Faults from the WSDL

    Declared faults arrive as answers, next to each operation's default response.

  2. Response or Fault

    The same answer editor; Fault adds code, reason and detail.

  3. Code and status

    Sender or Receiver (Client and Server for SOAP 1.1), sent with HTTP 500 unless you set another.

  4. Detail from the XSD

    The fault's detail element is a template, checked against the WSDL's fault type.

  5. What the app gets

    The whole envelope in the call's SOAP version, filled from the last call.

mTLS, ICP certificates and XML signatures

mTLS, ICP certificates and XML signatures: the SOAP screen in Stuntman
1Require a client certificate

On HTTPS a missing certificate fails the handshake; one not signed by the Test CA is refused.

1 of 5
2Must carry a CNPJ

ICP-Brasil style: the certificate needs OID 2.16.76.1.3.3. An e-CPF or an expired one fails.

2 of 5
3Check each request's signature

A tampered or unsigned document gets the signature_invalid answer, or a Sender fault.

3 of 5
4Sign the answers

The named element of each answer is signed with the service's own certificate. Faults are not signed.

4 of 5
5Test certificates

Synthetic e-CNPJ or e-CPF as .pfx and PEM; ask for an expired or untrusted one on purpose.

5 of 5
  1. Require a client certificate

    On HTTPS a missing certificate fails the handshake; one not signed by the Test CA is refused.

  2. Must carry a CNPJ

    ICP-Brasil style: the certificate needs OID 2.16.76.1.3.3. An e-CPF or an expired one fails.

  3. Check each request's signature

    A tampered or unsigned document gets the signature_invalid answer, or a Sender fault.

  4. Sign the answers

    The named element of each answer is signed with the service's own certificate. Faults are not signed.

  5. Test certificates

    Synthetic e-CNPJ or e-CPF as .pfx and PEM; ask for an expired or untrusted one on purpose.

Break it on purpose

The failures you need to test, exactly when you ask: from the screen or by a tool call, each one shown on the timeline with who caused it.

  • A declared fault

    Any fault the WSDL declares, on the next calls

    force_answer coverage_exceeded, or a decide rule
  • A fault it does not declare

    A new fault with your code, reason and detail

    set_answer fault={code, reason}
  • Validation fault

    A body that breaks the XSD gets the provider's Sender fault naming the field

    send a bad body, or tighten types
  • VersionMismatch

    A SOAP 1.1 envelope sent to a 1.2 service, or the reverse

    soap.version in the plugin
  • Refused credentials

    The security token could not be authenticated or authorized

    security: username_token and a wrong password
  • Refused XML signature

    A missing, broken or tampered ds:Signature

    set_service xml_signature_check
  • Refused client certificate

    No certificate, an e-CPF, an expired or an untrusted one fails the handshake

    set_service client_certificate_icp + new_test_certificate
  • Server fault

    500 goes out as a Receiver fault

    force_answer 500
  • Slow or dropped

    Latency, reset, empty, timeout, 503 or an HTML page

    force_answer, set_service latency
  • Unknown operation

    A SOAPAction the WSDL lacks gets a Sender fault and lands in Unmatched

    call it; list_unmatched

Why not the real sandbox

Your AI agent drives it

Claude Code, Codex or any MCP client connects to /mcp (or calls /api over plain HTTP), sets the stand-in up, breaks it on cue and reads what your app did.

you

Stand in for the insurer's SOAP service from its WSDL and check how we handle the coverage fault.

import_wsdl{"service": "example-insurance", "source": "https://insurance.example.com/PolicyService?wsdl"}
→ ok 4 operations, 3 faults, 1 callback
force_answer{"service": "example-insurance", "answer": "coverage_exceeded", "count": 1}
wait_for_api_call{"service": "example-insurance", "answer": "coverage_exceeded"}
→ ok RegisterShipment answered the CoverageExceeded fault, HTTP 500

MCP tools

  • import_wsdlA SOAP service from a WSDL (URL, file or text)
  • reimport_wsdlReads the WSDL again and keeps your steps
  • list_operationsOperations, SOAPActions and the served WSDL's URL
  • set_operationReplaces an operation's steps
  • try_operationRuns an envelope through the service; nothing is kept
  • send_callbackCalls the app's endpoint as the provider would
  • set_answerWith fault, makes an answer a SOAP fault
  • new_test_certificateAn ICP-Brasil style e-CNPJ or e-CPF test certificate
  • sign_xmlSigns an element of an XML document
  • verify_xml_signatureChecks every ds:Signature of a document

The same over HTTP

  • POST/api/plugins/wsdl
  • GET/api/plugins/{service}/operations
  • POST/api/plugins/{service}/operations/try
  • POST/api/plugins/{service}/callback
  • POST/api/apis/test-certificates
  • POST/api/apis/xml/sign