EasyLink Messaging API Namespaces
This table shows all the namespaces currently used and accepted by the EasyLink Messaging API web services. Links are provided for the schemas for each namespace, and to the WSDL files that use them.
Different usages of the EasyLink Messaging API call for different WSDLs. The most common usage is a synchronous web service call, in which the result of processing the request is contained in the response. Asynchronous usage requires two WSDLs - one used to submit the request and get an acknowledgement, and one that must be supported by a user-provided web service to receive the result of processing the request.
Older schemas and WSDLs defined many functions in one file. As the number of functions increased, this became awkward to maintain and use in development, so functions began to be assigned individual namespaces, although they were not removed from the older ones to avoid disturbing existing applications. Using older namespaces also incurs a slight performance penalty. The "current" namespaces (white background in the table) provide separate schemas and WSDLs for each function, and their use is strongly recommended.
Document delivery via a web services call ("web services push" or "WSDA") currently expects the receiving application to use the 2008/10 JobDocumentTransmit async results WSDL.
IMPORTANT: These links are only intended to permit downloading schemas and WSDLs for use during development. Schemas and WSDLs may also be obtainable using the namespace URL (with optional '?WSDL' parameter). These links and URLs should NOT be used to retrieve WSDLs at runtime, since their availablility cannot be assured. Application environments that require runtime loading of WSDLs should load them from a local location (file or server), and not from this site.