I am genuinely curious, to those still building SOAP based APIs in 2022, why??

  • 12
    Because the vendor is from the Stone Age and doesn't know wtf a rest api is.

    Plus, using an XSD for validating api data isn't a bad thing.
  • 5
    Jolly torturing of devs, why else?
  • 1
    envelope signature could be one of the reasons IMO
  • 1
    Because one of our clients has one old guy writing all of their APIs and only ever learnt SOAP and insists that it’s the only way they can write an API.
    It makes me sad every time I see it.

    Although I think there is an argument for using it in a few scenarios. Not in our case though.
  • 2
    Because the api standard for connecting brokers to insurance company systems for our country defines SOAP.
    And our team is tasked to write an service to provide such an endpoint and connect it to our internal system.
    Also, that standard has errors and inconsistencies.
  • 6
    SOAP itself isn't actually that terrible.

    the problem is the people usually using SOAP, because most of the time, _they're_ terrible. and they would make terrible APIs with REST, GraphQL, or any other paradigm/technology.
  • 0
    Upnp has is the only api my router understands.
  • 4
    I would say Dove maybe?

    They could build a soap API.

    GET /ingredients

    ["aqua", "stearic acid", "lauric acid", "sodium palmate", ...]
  • 1
    The reason is nostalgia. I really want to build something on PHP 5.4 and Apache in 2022, just because it brings me back in time when I was a student, the world was simpler, there was no war between my country and Ukraine, and I actually remembered what an integral equation is and how to solve them.
  • 1
    @bittersweet this is another example where HTTP 418 is a valid response
Add Comment