https://community.appian.com/discussions/f/integrations/12102/web-api-wsdlHi all! Might this be a silly question, so apologies in advance. We published a process model as a web service via the admin console (the legacy way, let&#39;s name it). In this way, getting the WSDL is quite clear. But it looks like this is not theen-USTelligent Community 12https://community.appian.com/thread/53626?ContentTypeID=1Fri, 23 Mar 2018 17:25:39 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:67e5ad6e-6086-43c4-a97c-162abd0c4894jordibOh, I see.<br /> We haven&#39;t found in the docs if the protocol was REST or SOAP, and as the legacy had WSDL we directly inferred the WEB API was the same.<div style="clear:both;"></div>https://community.appian.com/thread/53618?ContentTypeID=1Fri, 23 Mar 2018 13:21:48 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:11b86b91-6bf7-4c44-a4cf-bde0fb501ba0malcolm.rossAppian Web API Designer publishes RESTful APIs instead of SOAP APIs. REST APIs are lighter weight and do not have WSDLs associated with them. <br /> <br /> <a href="https://stackify.com/soap-vs-rest/">stackify.com/.../</a><div style="clear:both;"></div>