This document explains how to make Order Size Discounts API calls. It provides an overview of the formats and parameters you can use with the Order Size Discounts API.

Introduction to Service
Supported Request and Response Formats
- XML
- SOAP
Call Structure
Syntax
Testing Overview
Schema Location
User-Contributed Notes

Introduction to Service

Order Size Discounts is a SOA service that is intended to be consumed by sellers in the US, UK, and Germany. This service allows sellers to create and manage discount campaigns. Discount campaigns allow sellers to offer discounts to buyers based on order size (number of items in order or total order value). To be eligible for a discount, buyers must purchase the primary product and at least one related item in a product bundle. Product bundles assist sellers in increasing sales by marketing related items to buyers. The Order Size Discounts API has calls to create, update, retrieve, and delete discount campaigns. Additionally, the getVersion call simply returns the current version of the Order Size Discounts service.

Service Endpoints—The Order Size Discounts API has unique gateway URLs (service endpoints) for the Production environment and the Sandbox environment. The service endpoint includes the service version (e.g., v1). When updating to a new major version of the service, you must update to a new service endpoint as well.
HTTP headers and URL parameters—The Order Size Discounts API uses eBay's Service Oriented Architecture (SOA) framework and requires that an eBay authorization token is passed in through a (X-EBAY-SOA-SECURITY-APPNAME) header or (SECURITY-APPNAME) URL parameter.
Schema and data type notes—The Order Size Discounts API does not share schema or data types with other eBay APIs. In the API, you will find the following differences from other eBay APIs:
Naming conventions—The naming conventions for the Order Size Discounts API are slightly different than the Trading API. Most notably, call names and fields in the Related Items Management API begin with lowercase letters.
Versioning scheme—The version numbering scheme for the Order Size Discounts API is different from the scheme used by the eBay Shopping and Trading APIs. The Related Items Management API version consists of three digits (e.g., 1.2.3):
- The first digit indicates the major release version. Major releases are not backward compatible. eBay supports the two most recent major versions of the service. The service endpoints and target namespace include the major version of the service.
- The second digit indicates the minor release version. Minor releases consist of feature additions or behavior changes that are backward compatible.
- The third digit indicates the maintenance, or micro release version. Maintenance releases are used to correct minor problems. Maintenance releases have minimal impact on the features or functionality of the API. These changes may or may not have associated schema changes.

createCampaigns Call

For more information on the createCampaigns call, see the Users Guide.

deleteCampaigns Call

For more information on the deleteCampaigns call, see the Users Guide.

getCampaign Call

For more information on the getCampaign call, see the Users Guide.

getCampaigns Call

For more information on the getCampaigns call, see the Users Guide.

setCampaignStatus Call

For more information on the setCampaignStatus call, see the Users Guide.

updateCampaigns Call

For more information on the updateCampaigns call, see the Users Guide.

getVersion Call

For more information on the getVersion call, see the Users Guide.

Supported Request and Response Formats

The Order Size Discounts API supports XML and SOAP request and response formats.

XML

The HTTP POST call method supports the use of XML format requests.

<createCampaigns xmlns="http://www.ebay.com/marketplace/incentives/v1/services">
</createCampaigns>

SOAP

The HTTP POST call method also supports the use of SOAP format requests. SOAP versions 1.1 and 1.2 are both supported.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope" xmlns="http://www.ebay.com/marketplace/incentives/v1/services">
   <soap:Header/>
   <soap:Body>
      <createCampaigns>
      </createCampaigns>
   </soap:Body>
</soap:Envelope>

The call response for SOAP requests is in SOAP format only.

Call Structure

Each Order Size Discounts API call consists of the following elements:

Service Endpoint—Order Size Discounts API requests can be sent to either the Production API Gateway (endpoint) or the Sandbox endpoint for the Order Size Discounts API.
HTTP Headers or URL Parameters—Each Order Size Discounts API call requires a X-EBAY-SOA-SECURITY-APPNAME header or a SECURITY-APPNAME URL parameter. Similarly, you must always specify the call name in the X-EBAY-SOA-OPERATION-NAME header or OPERATION-NAME URL parameter. Other headers are optional or conditionally required.
Standard Input Fields—The ExtensionType field and its four child elements are the only standard input fields for calls in the Order Size Discounts API. These fields are optional.
Call-specific Fields—The input fields that are specific to a particular API call.

Service Endpoints

Order Size Discounts API requests may be sent to either the eBay Production API Gateway URI (endpoint) or the eBay Sandbox endpoint. You specify the endpoint in the request.

Production Endpoint:

https://svcs.ebay.com/services/incentives/v1/SellerDiscountOfferManagementService

Sandbox Endpoint:

http://svcs.sandbox.ebay.com/services/incentives/v1/SellerDiscountOfferManagementService

Note: The service endpoint contains the major version for the service (e.g., v1). When updating to subsequent major releases, you must update the version in the service endpoint, as well.

Standard URL Parameter or HTTP Header Values

When you make a Order Size Discounts API call, you choose whether to specify the standard values in URL parameters or in the HTTP headers. URL parameters are provided as name-value pairs in the query part of the URI.

Note: If you specify both a URL parameter and an HTTP header for the same value in the same call, the URL parameter takes precedence. The values you provide in your call are case-sensitive.

The following table contains descriptions of the standard Order Size Discounts API parameters and the corresponding header values:

URL Parameter Header Value Required? Description

N/A

CONTENT-TYPE

If you use this header, you must specify the content format exactly as shown, or your call may fail. The allowable values are:

XML	text/xml
SOAP12	application/soap+xml
SOAP11	text/xml (together with SOAPAction header being sent - value can be anything)

MESSAGE-ENCODING X-EBAY-SOA-MESSAGE-ENCODING Conditionally Specifies the message encoding (e.g., ISO-8859-1). The default encoding is UTF-8. When submitting requests in any format other than UTF-8, you must specify the message encoding.

N/A X-EBAY-SOA-MESSAGE-PROTOCOL Conditionally If you make a SOAP request, you must use this header to specify the protocol you are using. Allowable values are "SOAP11" for SOAP Version 1.1 and "SOAP12" for SOAP Version 1.2.

SERVICE-NAME X-EBAY-SOA-SERVICE-NAME No The name of the service you are using. Specify "SellerDiscountOfferManagementService" for all Order Size Discounts API calls.

OPERATION-NAME X-EBAY-SOA-OPERATION-NAME Yes The name of the call you are using (for example, createCampaigns or getCampaigns).

REQUEST-DATA-FORMAT X-EBAY-SOA-REQUEST-DATA-FORMAT No The Order Size Discounts API supports XML and SOAP request formats with the HTTP POST method. Input can be in XML or SOAP formats. The default value for HTTP POST requests is XML.
For SOAP requests, you must specify the protocol version in the X-EBAY-SOA-MESSAGE-PROTOCOL header. If you use a URL for an HTTP GET request, REQUEST-DATA-FORMAT is unnecessary because the only valid value is NV (Name-Value Pair).

RESPONSE-DATA-FORMAT X-EBAY-SOA-RESPONSE-DATA-FORMAT No If you use a URL (HTTP GET) request, use this parameter to specify the output format as XML. URL requests do not support SOAP responses. If you use a URL, and you do not specify RESPONSE- DATA-FORMAT, the output format will be XML. If you use the HTTP POST method, the output data (response data) will be in the same format as the input data.

REST-PAYLOAD N/A No If you use a URL, use this parameter to separate the payload part of the URL from the standard headers. Requires no value; anything appearing after this header will be considered part of the call payload. This parameter is ignored in HTTP POST requests.

SECURITY-APPNAME X-EBAY-SOA-SECURITY-APPNAME Yes This header is used to pass in the eBay authorization token, unique to the user's application. You obtain an eBay authorization token by joining the eBay Developer Network.

SERVICE-VERSION X-EBAY-SOA-SERVICE-VERSION No The API version your application supports (e.g., 1.1.0).

URL Parameter Examples

If you are using a URL (and the HTTP GET method), input must be in the NV (Name-Value Pair) format. Use the RESPONSE-DATA-FORMAT header to specify that data is returned in one of the following formats: NV or XML. The following example (wrapped for readability) shows standard Order Size Discounts API parameters. RESPONSE-DATA-FORMAT specifies XML for XML output.

https://svcs.ebay.com/services/incentives/SellerDiscountOfferManagementService/v1?OPERATION-NAME=createCampaigns
  &SERVICE-NAME=SellerDiscountOfferManagementService
  &SERVICE-VERSION=1.0.0
  &SECURITY-APPNAME=<eBayAuthToken>
  &RESPONSE-DATA-FORMAT=XML
  &REST-PAYLOAD
  &Standard input fields
  &Call-specific input fields

HTTP Header Examples

The following example shows standard Competitive Pricing API headers for an HTTP POST call using XML:

X-EBAY-SOA-SERVICE-NAME: SellerDiscountOfferManagementService
X-EBAY-SOA-OPERATION-NAME: createCampaigns
X-EBAY-SOA-SERVICE-VERSION: 1.0.0
X-EBAY-SOA-SECURITY-APPNAME: <eBayAuthToken>
X-EBAY-SOA-REQUEST-DATA-FORMAT: XML

The following example shows standard Order Size Discounts API headers for an HTTP POST call. In the example, the X-EBAY-SOA-REQUEST-DATA-FORMAT header specifies XML. The example also includes X-EBAY-SOA-MESSAGE-PROTOCOL: SOAP12, specifying that you are using SOAP Version 1.2. Without the X-EBAY-SOA-MESSAGE-PROTOCOL header, the service would expect XML input.

X-EBAY-SOA-SERVICE-NAME: SellerDiscountOfferManagementService
X-EBAY-SOA-OPERATION-NAME: createCampaigns
X-EBAY-SOA-SERVICE-VERSION: 1.0.0
X-EBAY-SOA-GLOBAL-ID: EBAY-US
X-EBAY-SOA-SECURITY-APPNAME: <eBayAuthToken>
X-EBAY-SOA-REQUEST-DATA-FORMAT: XML
X-EBAY-SOA-MESSAGE-PROTOCOL: SOAP12

Call-Specific Values

Refer to the Order Size Discounts API Call Reference for the input and output fields supported by the Order Size Discounts API calls.

Syntax

This section spells out the syntax requirements for the supported request and response formats. In most cases, the syntax for the various formats is standard and only the rules that aren't standard or are potentially tricky are explained.

XML Syntax
SOAP Syntax

UTF-8 Encoding for Special Characters

All parameter values should be encoded in UTF-8 format. UTF-8 is the default encoding for API requests.

Once the parameter value is UTF-8 encoded, it should be URL-encoded to take care of spaces and quotation marks (" ") and other characters in the string that are pertinent to the URL request.

When submitting requests in any format other than UTF-8, you must specify the message encoding with the MESSAGE-ENCODING URL parameter or the X-EBAY-SOA-MESSAGE-ENCODING HTTP header.

URL Encoding for String Values

Name-value requests must be constructed using the ASCII character-set only. Most ASCII characters (e.g., the numbers from 0-9 and the uppercase and lowercase English letters from A to Z) can be used as is. Some special characters, however, such as spaces, ampersands ("&") and quotation marks, must be encoded in URL requests when used in string values for fields.

Special characters that must be URL-encoded include (but are not limited to) characters used in URL request syntax, such as ampersands ("&"), the equals sign ("="), the pound sign ("#"), the "at" symbol ("@"), or the percent sign ("%").

URL-encoded characters are in the form %HH, where HH is a hexadecimal number. For example, the URL-encoded value for an ampersand is %26 and the URL-encoded value for a space is %20. The plus sign ("+") can also be used in place of spaces.

Many languages provide functions or methods to do the URL encoding for you. For example, PHP provides the rawurlencode function and Java provides URLEncoder class. For more information about URL encoding, see RFC 1738.

XML Syntax

The XML request/response format follows standard XML syntax conventions. Please see XML Syntax Rules on w3schools.com for more information.

SOAP Syntax

The SOAP request/response format follows standard SOAP syntax conventions. Please see SOAP Syntax on w3schools.com for more information.

Testing Overview

You can use the Sandbox environment (with the http://svcs.sandbox.ebay.com/services/incentives/v1/SellerDiscountOfferManagementService endpoint) to test calls to the Order Size Discounts API.

Schema Location

You can download the latest version of the WSDL for the Order Size Discounts API with the following link:

http://developer.ebay.com/webservices/order-size/latest/SellerDiscountOfferManagementService.wsdl

Alternatively, you can access a particular version of the Order Size Discounts schema using a URL with the following format (where VERSION is the version identifier of the release):

http://developer.ebay.com/webservices/order-size/VERSION/SellerDiscountOfferManagementService.wsdl

The version identifier is the version number of a particular schema (a release number).

For example, you can access version 1.0.0 of the WSDL version of the schema at the following URL:

http://developer.ebay.com/webservices/order-size/1.0.0/SellerDiscountOfferManagementService.wsdl

User-Contributed Notes

-->

Order Size Discounts API Making an API Call