Probably more one for the URLv2 monitor type but...
I have had nightmares in the past with vendors changing specs in ways that make their API not backward compatible, and having 'apps' or otherwise other code out there in the wild which is now unable to consume this API.
How I handled this previously was to write a script to consume the HTML of the SOAP WSDL response, and create a checksum (md5/sha1 etc) of the response. This fingerprint was then used to determine if anything about the service changed, since changing a spec changes the wsdl which changes the fingerprint. This was more robust than regex string matching when dealing with so much content and needing to track any change at all.
Ideally I would like to Setup a URLv2 check and in the check setup have it create a checksum of the page. Then if the check runs and produces a different checksum of the page contents - a fatal alert is raised.
Would be interested to hear your thoughts on this or thoughts around any particular methodologies or techniques where you think Apica can help with Native Smartphone App monitoring. We haven't really touched on this so far in the relationship.