This. So true! ...it almost always seems to come down to guesswork. Meanwhile, the vendor just exposes the WSDL and assumes that's sufficient "doc

This. So true! ...it almost always seems to come down to guesswork. Meanwhile, the vendor just exposes the WSDL and assumes that's sufficient "documentation" for clients and you don't need any examples or explanations or other info. I find the best way to approach this is to open Soap UI and start messing with settings until requests are accepted. There's no point asking the vendor for documentation because they probably don't know themselves. Having just dealt SOAP API last week, I can relate to this so much. I'm glad that I'm not the only one feeling the pain here.