SOAP API (Simple Object Access Protocol) is in some ways the predecessor to the REST API, but it is distinct from REST. SOAP is a protocol, while REST is a style.
The clearest analogy is in this Postman article, which compares SOAP to a National Postal Service: "(SOAP) is older, established, and dependable— but it can be slower than competing architectural styles like REST."
SOAP API requests and responses are formatted with XML, and while extensible, areand more bandwidth intensive than REST. Like REST, they are transmitting with HTTP, but can also use SMTP, TCP, and UDP, which can be a big benefit in the right use cases.
While XML allows for data to be described any way you like, the SOAP schema requires a specific structure around that data.
Not at all. While REST API's are common (e.g., all Abstract's APIs use REST), SOAP is still widely used, especially in enterprise and banking applications, where the strict contracts of XML schema maintain stability and structure in responses and requests. It requires more bandwidth to transmit verbose XML states with every request, but is a worthwhile tradeoff for security and functionality.
REST APIs are extremely popular, but SOAP APIs do offer a lot of functionality out of the box that REST APIs do not. They are also a good place to start if you are just learning web development, because their stricter formatting requirements are more instructional than REST, akin to learning C++ before learning Python.