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

!rant

Dev walked out of the bathroom stall (I can only assume it was the #2), only washed one hand.
One hand under the auto-soap dispenser, then kinda rinsed the soap off. The other hand never got involved.

That seems weird to me.

I am implementing an API. How do I know what to do? Read the docs! Unless... there's none on the website. Asked by email and they could provide a PDF, which contains some graphics which you're free to interpret ...
Machine readable description? Nope.
How do I get to know about updates to the API? *blank stare*

A friend recommended Durrell's "The Alexandria Quartet" in 1982. I check it out from the library and read it. Over the intervening years I acquired a very nice softcover edition. Last Christmas I began reading it again. For some reason I was pissed off at the soap opera bassinet who haven't we bonked narrative that began the fourth book.
So I ripped up the softcover edition and threw it away. Now I'm re-reading the third book. I wanted to buy just that one. Except it's something like forty dollars. I learnt my lesson. Don't tear up good softcover editions of books just because you don't like them at the mo. It'll cost ya.

4 hours wasted due to a rather strange "scope poisoning" bug... it was really fucking strange.
Had to move the 5 lines of code, above where the error happened, to a private function.
The 5 lines just called an XLSX library which read a given file and returned an array. I don't know how but the thing somehow messed with my Soap client call one line below. The culprit must have been some IO resource handle which didn't get destroyed when in the same scope due to persisting object references..