Amazon DevPay
Developer Guide (API Version 2007-12-01)

SOAP Requests


Amazon DevPay is not accepting new seller accounts at this time. Please see AWS Marketplace for information on selling your applications on Amazon Web Services.

The License Service supports the SOAP message protocol for calling service actions over an HTTPS connection. The easiest way to use the SOAP interface with your product is to use a SOAP toolkit appropriate for your programming platform. SOAP toolkits are available for most popular programming languages and platforms.


All requests to the License Service must be made using HTTPS. HTTP requests are not accepted.

The service's Web Services Description Language (WSDL) file describes the actions along with the format and data types of the actions' requests and responses. For the location of the WSDL, see WSDL Location. Your SOAP toolkit interprets the WSDL file to provide your product access to the actions. For most toolkits, your product calls a service action using routines and classes provided or generated by the toolkit.

The topics for each of the License Service actions describe the request parameters for each action and their values. You might find it useful to refer to the WSDL file directly to see how the parameters appear in the XML of the request generated by your toolkit, and to understand how your toolkit makes the actions available to your product code.

Structure of a SOAP Request

A SOAP request is an XML data structure that your SOAP toolkit generates and sends to the service. As described by the service WSDL, the root element of this structure is named after the License Service action. You include the parameters for the request inside the root element, according to the WSDL.

The following example shows the XML for a SOAP message that calls the ActivateHostedProduct action. Although you probably won't manually build the SOAP message for a service request, it is useful to see what your SOAP toolkit tries to produce when provided with the appropriate values. Many SOAP toolkits require you to build a request data structure similar to the XML to make a request.

<?xml version="1.0" encoding="UTF-8" ?> <soapenv:Envelope xmlns:soapenv="" xmlns:xsd="" xmlns:xsi=""> <soapenv:Body> <ActivateHostedProduct xmlns=""> <ActivationKey>ADMAY7DVLJTWHJ76MMBMQEXAMPLE</ActivationKey> <ProductToken>{ProductToken}AAAHVXNlclRrbgfOpSykBA....[long encoded token]...</ProductToken> </ActivateHostedProduct> </soapenv:Body> <timestamp> <Created>2007-06-09T10:57:35Z</Created> <Expires>2007-06-09T11:02:35Z</Expires> </Timestamp> </soapenv:Envelope>