Skip to main content
2026-07-29 16:01
SOAP

Basic SOAP Request

RequestParseValidateEasy
Try Interactive Demo

What you will learn

  • Namespace declarations on the SOAP envelope are non-negotiable — missing soapenv:Envelope namespace is the top bug
  • Content-Type must be text/xml; charset=utf-8 for SOAP 1.1, application/soap+xml for 1.2 — servers reject the wrong one silently
  • Test SOAP Fault responses as a first-class path — fault code + faultstring have structure, your client must parse it

Description

Send a SOAP envelope to call GetUser operation.

Test Scenario

const envelope = `
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetUser xmlns="http://practice.api">
      <id>1</id>
    </GetUser>
  </soap:Body>
</soap:Envelope>`;

const response = await request.post('/api/soap', {
  headers: { 'Content-Type': 'text/xml' },
  data: envelope
});
Endpoint/api/soap

Testing Tips

  • •Use Content-Type: text/xml
  • •Include SOAP envelope wrapper
  • •Match namespace from WSDL
// Playwright API Testing - SOAP
import { test, expect } from '@playwright/test';


test('SOAP request', async ({ request }) => {
  const soapEnvelope = `<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetUsers xmlns="http://api.example.com/"/>
  </soap:Body>
</soap:Envelope>`;


  const response = await request.post('/api/soap', {
    headers: { 'Content-Type': 'text/xml' },
    data: soapEnvelope
  });


  expect(response.ok()).toBeTruthy();
  const text = await response.text();
  expect(text).toContain('soap:Envelope');
});

Challenge ID: soap-basic-request

2 frameworks available

API Playground

Send requests and inspect responses

Endpoint: /api/soap

Press Enter to send