Definitely a REST Service...

You can tell by looking for the SOAP envelope if they show a request trace (as they do in the docs). It the document is plain XML (or JSON) without a SoapEnvelope that includes the method name and body wrappers you know you're NOT dealing with SOAP.

SOAP can be a pain to deal with - a lot more ceremony in the protocol - if you do it manually, but if you use tooling (like the West Wind Web Service Proxy Generator) that capitalize on reading the WSDL structure and providing you a client object model, rather than raw data parsing, it can be easier to use more complex services. The issue with REST - especially if you use an XML based REST service is that you still have to parse the XML into somehting you can use, while a WSDL tools typically let you work with objects. JSON is a little easier because there are better JSON mappers for FoxPro, while XML still remains a manual process to parse (due to the complexity of the XML spec and schema matching where JSON is a simple data model with a few known types).

+++ Rick ---

>Hi
>
>This may be a daft question !
>
>I need to access a web service through a package (SCRIBE Insight) which has a SOAP web service adaptor. How can I tell if the web service is a SOAP webservice or a REST service ? I can't find a WSDL so I'm thinking its REST.
>
>This is the details of the web service
>
>https://developer.concur.com/get-started/webservices-overview