Two integration styles that are not really competitors any more — and why enterprise work still meets both.
SOAP is a protocol: XML messages with a formal contract (WSDL), built-in standards for security and transactions, and strict validation. REST is an architectural style: HTTP verbs against resources, usually JSON, with the contract described separately. New work is overwhelmingly REST. SOAP persists where it is embedded in enterprise systems and banking interfaces.
For new development the question rarely arises — REST, or increasingly GraphQL or gRPC. The reason it still matters is integration: SAP, Oracle, banks and government portals expose SOAP services that are not going away, so an integration layer has to speak both. Treating SOAP as obsolete rather than as something you will encounter leads to surprises mid-project.
SOAP has WSDL, machine-readable and strict. REST commonly uses OpenAPI, which is descriptive rather than enforced.
SOAP is XML with an envelope. REST is usually JSON, smaller and easier to read and debug.
SOAP has standard faults. REST uses HTTP status codes plus a body convention, which varies between APIs.
SOAP has WS-Security for message-level signing and encryption. REST generally relies on TLS plus OAuth tokens.
SOAP has standards for distributed transactions. REST does not, which is usually fine and occasionally is not.
A business needs two integrations. The first is a mobile app fetching customer orders. The second is a payment instruction to a bank.
For the mobile app, REST is the obvious fit: lightweight JSON over HTTP, cacheable, easy to consume from any client, no code generation needed, and small payloads matter on mobile data. SOAP would add XML parsing overhead and ceremony for no benefit the app can use.
For the bank, the requirements are different in kind. There is a formal contract both parties must honour, message-level signing so the instruction is provably from you, non-repudiation, and a guarantee the message is processed exactly once. SOAP with WS-Security was designed for precisely this, and the bank's interface specification will almost certainly require it. Choosing REST here would mean rebuilding those guarantees by hand, badly. The useful framing is not that one style is modern and the other legacy — it is that formal contracts and message-level security still have a home.
| Term | What it means |
|---|---|
| REST | An architectural style using HTTP verbs against resource URLs, usually exchanging JSON. |
| SOAP | A protocol with a strict XML envelope, formal contracts and extensive standards. |
| WSDL | The machine-readable contract describing a SOAP service, from which clients can be generated. |
| OpenAPI | The equivalent specification format for REST, though descriptive rather than enforced. |
| WS-Security | The SOAP standard for message-level security, including signing and encryption. |
Enterprise integration still meets SOAP regularly. Scope it before committing to a timeline.
Without OpenAPI, consumers guess. The contract is not optional just because the style does not enforce it.
Where a payload must be signed independently of transport, TLS alone does not satisfy the requirement.
Some APIs return 200 with an error in the body. Check the body, not only the status.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Payload size | Directly affects mobile and high-volume performance. XML envelopes are substantially heavier. | |
| Error rate by type | Contract violations, authentication failures and business errors need separating. | |
| Average response time | Per endpoint or operation, not averaged across the service. | |
| Contract version drift | Clients running against older versions, which constrains when you can change anything. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.