-
Download the WSDL files and the schema file from the Vindicia servers.
Note: Depending on your integration needs, you might not need all the WSDL files. Feel free to consult with Vindicia Client Services to decide which ones you need. See the Subscribe API Guide for the objects and the methods supported by the WSDL files.
For Subscribe API production releases, download from the following sites:
-
WSDL file:
https://soap.vindicia.com/*version/object*.wsdl, for example,https://soap.vindicia.com/4.2/PaymentMethod.wsdl -
Schema file:
https://soap.vindicia.com/version/Vindicia.xsdFor Subscribe API nonproduction releases that are in Vindicia’s staging servers for testing prerelease client regression, download from the following sites: -
WSDL file:
https://soap.staging.sj.vindicia.com/version/object.wsdl -
Schema file:
https://soap.staging.sj.vindicia.com/version/Vindicia.xsd
-
WSDL file:
- Optional. Update the SOAP endpoint address to reflect the server to which to send your SOAP calls, assuming that you cannot programmatically do so in your client code.
-
Generate local stub or proxy objects with language-specific tools. For example:
- If you program in Java and are using the Apache Axis library to work with SOAP, generate local stub objects with the utility
WSDL2Java. - If you program in .Net with C#, import the WSDL files into your project to automatically generate local stub objects.
- If you program in another language, such as Python, for which no appropriate tools are available, consult the language- or package-specific SOAP documentation on how client code can make the SOAP calls as described in the WSDL files.
- If you program in Java and are using the Apache Axis library to work with SOAP, generate local stub objects with the utility
- Ensure that your SOAP library supports making SOAP calls to external servers through HTTPS. For security, Vindicia does not support HTTP-based SOAP calls. You might need to install additional SSL-specific libraries on your system.
Performing the Prerequisite Steps
Before developing client code with the Subscribe WSDL files:

