To access the SOAP API, you need a Web Service Description Language (WSDL) file. The WSDL file defines the Web service that is available to you. Your development platform uses this WSDL to generate an API to access the IBM Web Service it defines. You can obtain the WSDL file via the following URL:

6 Not available
7 Not available
8 Not available
9 Not available
A Not available

Each functional area described above has its own XML namespace and schema. All schemas are located at
http://api[pod] The table below lists the available namespaces and schemas.

Functional Area Namespace Schema
Session Management SilverpopApi:EngageService.SessionMgmt.Login SessionMgmt1.xsd
List Management SilverpopApi:EngageService.ListMgmt.RecipientActions ListMgmt2.xsd
List Management User Actions SilverpopApi:EngageService.ListMgmt.UserActions ListMgmt‐
Mailing Mangement SilverpopApi:EngageService.MailManagement MailMgmt2.xsd
Mailing Management User Actions SilverpopApi:EngageService.MailManagement.UserActions MailMgmt‐
Reporting SilverpopApi:EngageService.Reporting Reporting1.xsd

For each method listed in this document that has special usage with Non‐Email‐Key Lists (NEK Lists), there is a section describing usage with NEK lists. Also see the Frequently Asked Questions section of the Appendices for more information on using Engage SOAP API with NEK lists.

Note: NEK lists are only available for organizations with the Non‐Email‐Key option enabled.

Join The Discussion

Your email address will not be published. Required fields are marked *