The XML and SOAP versions of the Trading API are based on the same schema.

  • When using the XML API, use ebaySvc.xsd for request validation and in conjunction with some XML tools that recognize the format.
  • When using the SOAP API, eBay API interfaces and proxies must be generated from ebaySvc.wsdl. Refer to Generate interfaces and proxies from a WSDL for additional information.

    The eBay WSDL defines the message signatures along with the service location information. Review the eBaySvc.wsdl file for more information.

    In the WSDL, the message elements define the request and response messages and the data types to use in the body of those messages. The message names are the same as the data type element names (e.g., AddItemRequest).

    • In the portType clause, you will find the name of the service definition interface (i.e., the interface that will be used to access operations,) which is derived from eBayAPIInterface. This interface specifies each logical operation (e.g., AddItem,) and indicates that they are bidirectional (i.e., request-response).
    • In the binding clause, you will find the name of the proxy that implements the service definition interface which is derived from eBayAPISoapBinding. The binding indicates that each operation needs to be transmitted using the SOAP document-literal style.
    • In the service clause, you will find the name of the service locator in the Production environment which is derived from eBayAPIInterfaceService. The service locator specifies the physical location of the service endpoint (i.e., the URI of the service provider—eBay's Production SOAP API gateway). This value must be overridden when executing calls in the Sandbox. Therefore, in general, it is a good idea to manually set the endpoint rather than obtaining it from the service locator.