SOAP and WSDL
Understand the envelope, the contract and when SOAP is still required.
What you will be able to do
- The Envelope is the mandatory root.
- WSDL describes the service contract.
- SOAP faults are structured errors.
- Prefer REST for new public APIs unless a contract requires SOAP.
In plain English
SOAP wraps messages in an Envelope with an optional Header and a Body. A WSDL document describes the operations, messages and endpoint. SOAP still appears in banking, government and enterprise integrations where a formal contract is required.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<GetCourse xmlns="https://example.com/courses">
<slug>css</slug>
</GetCourse>
</soap:Body>
</soap:Envelope>Your turn
MediumAdd a SOAP body
Wrap a GetCourse element in a SOAP Body.
HTML · starter
<soap:Envelope>Check your understanding before moving on.
Knowledge checkQuestion 1
Which element is mandatory in every SOAP message?
Select an answer to continue
Study tools
Make it yours.
Keep a private note for this lesson, then turn the key ideas into flashcards you can revisit.
Sign in to save notes and flashcards.Both are private to your account and stay with your progress.
Sign inFinished reading?
Lock in what you just learned.
0%
Mark this lesson complete to save your place and move one step closer to the certificate.