NetServer web service custom proxies
•
Environment: onsite
Some tooltip text!
• 1 minute to read
• 1 minute to read
If you are not developing solutions using Microsoft .NET and can't reference the SuperOffice assemblies, you must rely on your technology stack to either generate SOAP proxies or roll your own.
In many cases, such as PHP and Python, applications depend on loading the WSDL file for interacting with SuperOffice web services. We make those files available for downloads along in the SOAP web services API reference.
With the WSDL files and using a tool like SOAPUI, raw SOAP requests are sent to SuperOffice endpoints for testing. You can, for example, use SOAPUI or compose the SOAP request manually with Fiddler2:
