<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions 
	xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
	xmlns:xs="http://www.w3.org/2001/XMLSchema" 
	xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" 
	xmlns:ns="urn:ebay:apis:eBLBaseComponents" 
	xmlns="urn:ebay:apis:eBLBaseComponents"
	targetNamespace="urn:ebay:apis:eBLBaseComponents">
	<wsdl:types>
<!-- Version 821 -->
<!-- (c) 2004-2013 eBay, Inc. All rights reserved -->
		<xs:schema targetNamespace="urn:ebay:apis:eBLBaseComponents"  
		xmlns:ns="urn:ebay:apis:eBLBaseComponents" 
		xmlns="urn:ebay:apis:eBLBaseComponents"
		xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

	<!-- Custom Security header element-->
	<xs:element name="RequesterCredentials" type="ns:CustomSecurityHeaderType">
		<xs:annotation>
			<xs:documentation>
				Authentication information for the user on whose behalf the
				application is making the request. Only registered eBay users are
				allowed to make API calls. To verify that a user is registered,
				your application needs to pass a user-specific value called an
				"authentication token" in the request. This is equivalent to
				signing in on the eBay Web site. As API calls do not pass session
				information, you need to pass the user's authentication token every
				time you invoke a call on their behalf. All calls require an
				authentication token, except the calls you use to retrieve a token
				in the first place. (For such calls, you use the eBay member's
				username and password instead.)
			</xs:documentation>
			<xs:appinfo>
				<CallInfo>
					<AllCalls/>
					<RequiredInput>Yes</RequiredInput>
				</CallInfo>
			</xs:appinfo>
		</xs:annotation>
	</xs:element>
		<!--  Call: AddDispute -->
	<xs:element name="AddDisputeRequest" type="ns:AddDisputeRequestType"/>
	<xs:complexType name="AddDisputeRequestType">
		<xs:annotation>
			<xs:documentation>
				This call enables a seller to create an Unpaid Item case against a buyer, or to cancel a
				single line item order. 
				&lt;br/&gt;&lt;br/&gt;
				&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
				This call is only used by sellers to create an Unpaid Item case or to mutually cancel a
				single line item order. Buyers must use the eBay Resolution Center or PayPal Resolution 
				Center (for orders that satisfy requirements) to create an Item Not Received or an Item
				Significantly Not as Described case. 
				&lt;/span&gt;
			</xs:documentation>
			<xs:appinfo>
				<Summary>
				 Creates an Unpaid Item dispute against a buyer or 
				 cancels a single line item order.
				</Summary>
				<SeeLink>
					<Title>Unpaid Item Disputes</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UnpaidItemDisputes</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="DisputeExplanation" type="ns:DisputeExplanationCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This enumerated value gives the explanation of why the buyer or seller opened a
								case (or why seller canceled an order line item). Not all values contained in 
								&lt;b&gt;DisputeExplanationCodeType&lt;/b&gt; are allowed in the 
								&lt;b&gt;AddDispute&lt;/b&gt; call, and the values that are allowed must match 
								the &lt;b&gt;DisputeReason&lt;/b&gt; value.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDispute</CallName>
									<RequiredInput>Yes</RequiredInput>
									<allValuesExcept>PaymentMethodNotSupported, ShipCountryNotSupported, Unspecified, UPIAssistance, UPIAssistanceDisabled</allValuesExcept>
								</CallInfo>
								<SeeLink>
									<Title>Creating and Managing Disputes With Trading API</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UsingAddDispute</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DisputeReason" type="ns:DisputeReasonCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The type of dispute being created. &lt;b&gt;BuyerHasNotPaid&lt;/b&gt; and
								&lt;b&gt;TransactionMutuallyCanceled&lt;/b&gt; are the only values that may
								be used with the &lt;b&gt;AddDispute&lt;/b&gt; call. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDispute</CallName>
									<RequiredInput>Yes</RequiredInput>
									<onlyTheseValues>BuyerHasNotPaid, TransactionMutuallyCanceled</onlyTheseValues>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. A listing can have multiple
								orders, but only one &lt;b&gt;ItemID&lt;/b&gt;. To
								identify a specific order line item, either an
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair or an
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value must be passed in the request. So,
								unless &lt;b&gt;OrderLineItemID&lt;/b&gt; is used, this field is required.
							&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (ItemIDs usually consist of 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>AddDispute</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of an order line item. An order line item is created once
								a buyer purchases the item through a fixed-priced listing or by using the Buy It
								Now feature in an auction listing, or when an auction listing ends with a
								winning bidder. To identify a specific order line item, either an 
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair or an 
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value must be passed in the request. So,
								unless &lt;b&gt;OrderLineItemID&lt;/b&gt; is used, this field is required.
							&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>AddDispute</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier of an order line item,
								and is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and 
								&lt;b&gt;TransactionID&lt;/b&gt;, with a hyphen in between these two IDs. To 
								identify a specific order line item, either an 
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair or an 
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value must be passed in the request. So,
								unless &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is used,
								this field is required.
							&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50</MaxLength>
								<CallInfo>
									<CallName>AddDispute</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddDispute -->
	<xs:element name="AddDisputeResponse" type="ns:AddDisputeResponseType"/>
	<xs:complexType name="AddDisputeResponseType">
		<xs:annotation>
			<xs:documentation>
				Type defining the response of the &lt;b&gt;AddDispute&lt;/b&gt; call. Upon a successful 
				call, the response contains a newly created DisputeID value, which confirms that the 
				the Unpaid Item or Mutually Canceled Transaction case was successfully created.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="DisputeID" type="ns:DisputeIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of the Unpaid Item or Mutually Canceled Transaction case 
								that was successfully created with the &lt;b&gt;AddDispute&lt;/b&gt; call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDispute</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddDisputeResponse -->
	<xs:element name="AddDisputeResponseRequest" type="ns:AddDisputeResponseRequestType"/>
	<xs:complexType name="AddDisputeResponseRequestType">
		<xs:annotation>
			<xs:documentation>
				Allows a seller to respond to or close an Item Not Received dispute.
				This can be used to add a comment to an Unpaid Item Dispute
				only if the request version was lower than 637 when the
				dispute was created.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Adds a response or comment to a dispute, or closes a dispute.
				</Summary>
				<SeeLink>
					<Title>Unpaid Item Disputes</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UnpaidItemDisputes</URL>
				</SeeLink>
				<SeeLink>
					<Title>Buyer Disputes</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BuyerDisputes</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="DisputeID" type="ns:DisputeIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of the dispute,
								returned when the dispute was created.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDisputeResponse</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MessageText" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The text of a comment or response being posted to the dispute. Required
								when DisputeActivity is SellerAddInformation, SellerComment, or
								SellerPaymentNotReceived; otherwise, optional.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDisputeResponse</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DisputeActivity" type="ns:DisputeActivityCodeType"  minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The type of activity the seller is taking on the dispute. The allowed value is
								determined by the current value of DisputeState, returned by GetDispute or
								GetUserDisputes. Some values relate to Unpaid Item disputes and other values relate
								to buyer-created disputes known as Item Not Received or Significantly Not As
								Described disputes.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDisputeResponse</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>Unpaid Item Disputes</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UnpaidItemDisputes</URL>
								</SeeLink>
								<SeeLink>
									<Title>Buyer Disputes</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BuyerDisputes</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingCarrierUsed" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The shipping carrier used to ship the item in dispute. Non-alphanumeric
								characters are not allowed. This field (along with ShipmentTrackNumber) is
								required if DisputeActivity is SellerShippedItem.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDisputeResponse</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShipmentTrackNumber" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The tracking number associated with one package of a shipment. The seller is
								responsible for the accuracy of the shipment tracking number, as eBay only
								verifies that the tracking number is consistent with the numbering scheme
								used by the specified shipping carrier, but cannot verify the accuracy of
								the tracking number. This field (along with ShippingCarrierUsed) is required
								if DisputeActivity is SellerShippedItem.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDisputeResponse</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This timestamp indicates the date and time when the item under dispute was
								shipped. This field is required if DisputeActivity is SellerShippedItem.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddDisputeResponse</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddDisputeResponse -->
	<xs:element name="AddDisputeResponseResponse" type="ns:AddDisputeResponseResponseType"/>
	<xs:complexType name="AddDisputeResponseResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to a call of AddDisputeResponse.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddFixedPriceItem -->
	<xs:element name="AddFixedPriceItemRequest" type="ns:AddFixedPriceItemRequestType"/>
	<xs:complexType name="AddFixedPriceItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Defines and lists a new fixed-price listing (not auction-style listings).
				The main difference between AddFixedPriceItem and AddItem is that
				AddFixedPriceItem supports the creation of fixed-price listings only,
				whereas AddItem supports all listing formats.&lt;br&gt;
				&lt;br&gt;
				Also, only AddFixedPriceItem supports multi-variation listings
				and tracking inventory by SKU. AddItem does not support
				Variations or InventoryTrackingMethod.&lt;br&gt;
				&lt;br&gt;
				See the AddFixedPriceItem documentation for additional information.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Defines and lists a new fixed-price item. A fixed-price listing
					can include multiple identical items.
				</Summary>
				<RelatedCalls>
					AddItem, AddItems, AddToItemDescription, EndFixedPriceItem,
					GetItem, GetCategories, RelistFixedPriceItem,
					ReviseFixedPriceItem, VerifyAddFixedPriceItem
				</RelatedCalls>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ListingAnItem</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ListingItemsIntro</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
				<SeeLink>
					<Title>Multi-Variation Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Variations</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ConsideringBestMatch</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Root container holding all values that define a new
								fixed-price listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddFixedPriceItem -->
	<xs:element name="AddFixedPriceItemResponse" type="ns:AddFixedPriceItemResponseType"/>
	<xs:complexType name="AddFixedPriceItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the item ID, SKU (if any), listing recommendations (if applicable), the
				estimated fees for the new listing (except the Final Value Fee, which isn't calculated
				until the item has sold), the start and end times of the listing, and other details.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for the new fixed-price listing.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Item-level SKU for the new listing, if the seller specified
							Item.SKU in the request. Variation-level SKUs are not returned
							(see GetItem instead).
						</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Starting date and time for the new listing. This value is based
								on the time the listing was received and processed, or the
								time the item will be listed if the seller specified
								Item.ScheduleTime in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time when the new listing ends. This is the starting time
								plus the listing duration.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the new item listing.
								The fees do not include the Final Value Fee (FVF), which cannot be determined
								until an item is sold.
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>eBay.com Fees</Title>
									<URL>http://pages.ebay.com/help/sell/fees.html</URL>
								</SeeLink>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>Final Value Fees and Credits</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FinalValueFeesAndCredits</URL>
								</SeeLink>
								<SeeLink>
									<Title>Final Value Fees</Title>
									<URL>http://pages.ebay.com/help/sell/fvf.html</URL>
								</SeeLink>
								<SeeLink>
									<Title>Fees per Site</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeesPerSite</URL>
								</SeeLink>
								<SeeLink>
									<Title>Using Feature Packs to Save on Upgrade Fees</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UsingFeaturePacks</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the primary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID you passed in PrimaryCategory was mapped to a new ID by eBay.
								If the primary category has not changed or if it has expired with no replacement,
								CategoryID does not return a value.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the secondary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID you passed in SecondaryCategory was mapped to a new ID by eBay.
								If the secondary category has not changed or it has expired with no replacement,
								Category2ID does not return a value.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DiscountReason" type="ns:DiscountReasonCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The nature of the discount, if a discount is applied.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSuggestions" type="ns:ProductSuggestionsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides a list of products recommended by eBay which match the item information
								provided by the seller.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingRecommendations" type="ns:ListingRecommendationsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of one or more &lt;b&gt;Recommendation&lt;/b&gt; containers. 
								Each &lt;b&gt;Recommendation&lt;/b&gt; container provides a message to the 
								seller on how a listing can be improved or brought up to standard in reqards to 
								Top-Rated Plus listing requirements, Item Specifics, picture requirements, and/or 
								a recommendation to use a product code to list the item, such as a UPC, an EAN, or 
								an ISBN. 
								&lt;br&gt;&lt;br&gt;
								This container is only returned if the &lt;b&gt;IncludeRecommendations&lt;/b&gt; 
								flag was included and set to 'true' in the &lt;b&gt;AddFixedPriceItem&lt;/b&gt; request, and if 
								at least one listing recommendation exists for the newly created listing. If
								one or more listing recommendations are returned, it will be at the seller's 
								discretion about whether to revise the item based on eBay's listing 
								recommendation(s).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddItem -->
	<xs:element name="AddItemRequest" type="ns:AddItemRequestType"/>
	<xs:complexType name="AddItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Defines a single new item and lists it on a specified eBay site.&amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;.
				Returns the item ID for the new listing, and returns fees the seller will incur for the
				listing (not including the Final Value Fee, which cannot be calculated until
				the item is sold).
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddFixedPriceItem, AddItems, AddToItemDescription, GetItem,
					GetSellerList, RelistItem, ReviseItem,
					VerifyAddItem
				</RelatedCalls>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ListingAnItem</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ListingItemsIntro</URL>
				</SeeLink>
				<SeeLink>
					<Title>Specifying Shipping Costs when Creating or Revising a Listing</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/ManagingShipping-Specifying_Shipping_Costs_when_Creating_or_Revising_a_Listing.html</URL>
				</SeeLink>
				<SeeLink>
					<Title>Seller Checklist</Title>
					<URL>http://pages.ebay.com/sell/April2009Update/Checklist/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ConsideringBestMatch</URL>
				</SeeLink>
				<AddToDefaultAreas>half</AddToDefaultAreas>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Root container holding all values that define a new
								listing.
								&lt;br&gt;
								&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddItem -->
	<xs:element name="AddItemResponse" type="ns:AddItemResponseType"/>
	<xs:complexType name="AddItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the Item ID, SKU (if any), listing recommendations (if applicable), the
				estimated fees for the new listing (except the Final Value Fee, which isn't calculated
				until the item has sold), the start and end times of the listing, and other details.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for the new listing.
								&lt;br&gt;
								&lt;br&gt;
								Applicable to Half.com.
								&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
									Although eBay represents Item IDs as strings in the schema, we recommend you store
									them as 64-bit signed integers. If you choose to store Item IDs as strings, allocate
									at least 19 characters (assuming decimal digits are used) to hold them. eBay will
									increase the size of IDs over time, and your code should be prepared to handle IDs of
									up to 19 digits. For more information about Item IDs, see &lt;a href="
									http://ebay.custhelp.com/cgi-bin/ebay.cfg/php/enduser/std_adp.php?p_faqid=468"&gt;
									Common FAQs on eBay Item IDs and other eBay IDs&lt;/a&gt; in the Knowledge Base.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Starting date and time for the new listing.
								&lt;br&gt;
								&lt;br&gt;
								Applicable to Half.com (for Half.com, the start time is always the time the item was listed).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time when the new listing ends. This is the starting time plus the listing
								duration.
								&lt;br&gt;
								&lt;br&gt;
								Applicable to Half.com (for Half.com the actual end time is GTC, not the end time
								returned in the response).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the new item listing.
								The fees do not include the Final Value Fee (FVF), which cannot be determined
								until an item is sold.
								&lt;br&gt;
								&lt;br&gt;
								Applicable to Half.com, but the values are not applicable to Half.com listings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>eBay.com Fees</Title>
									<URL>http://pages.ebay.com/help/sell/fees.html</URL>
								</SeeLink>
								<SeeLink>
									<Title>Final Value Fees and Credits</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FinalValueFeesAndCredits</URL>
								</SeeLink>
								<SeeLink>
									<Title>Final Value Fees</Title>
									<URL>http://pages.ebay.com/help/sell/fvf.html</URL>
								</SeeLink>
								<SeeLink>
									<Title>Fees per Site</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeesPerSite</URL>
								</SeeLink>
								<SeeLink>
									<Title>Using Feature Packs to Save on Upgrade Fees</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UsingFeaturePacks</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the primary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID you passed in PrimaryCategory was mapped to a new ID by eBay.
								If the primary category has not changed or it has expired with no replacement,
								CategoryID does not return a value.
								&lt;br&gt;
								&lt;br&gt;
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the secondary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID you passed in SecondaryCategory was mapped to a new ID by eBay.
								If the secondary category has not changed or it has expired with no replacement,
								Category2ID does not return a value.
								&lt;br&gt;
								&lt;br&gt;
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DiscountReason" type="ns:DiscountReasonCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The nature of the discount, if a discount applied.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSuggestions" type="ns:ProductSuggestionsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides a list of products recommended by eBay which match the item information
								provided by the seller.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingRecommendations" type="ns:ListingRecommendationsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of one or more &lt;b&gt;Recommendation&lt;/b&gt; containers. 
								Each &lt;b&gt;Recommendation&lt;/b&gt; container provides a message to the 
								seller on how a listing can be improved or brought up to standard in reqards to 
								Top-Rated Plus listing requirements, Item Specifics, picture requirements, and/or 
								a recommendation to use a product code to list the item, such as a UPC, an EAN, or 
								an ISBN. 
								&lt;br&gt;&lt;br&gt;
								This container is only returned if the &lt;b&gt;IncludeRecommendations&lt;/b&gt; 
								flag was included and set to 'true' in the &lt;b&gt;AddItem&lt;/b&gt; request, and if 
								at least one listing recommendation exists for the newly created listing. If
								one or more listing recommendations are returned, it will be at the seller's 
								discretion about whether to revise the item based on eBay's listing 
								recommendation(s).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddItemFromSellingManagerTemplate -->
	<xs:element name="AddItemFromSellingManagerTemplateRequest" type="ns:AddItemFromSellingManagerTemplateRequestType"/>
	<xs:complexType name="AddItemFromSellingManagerTemplateRequestType">
		<xs:annotation>
			<xs:documentation>
				Creates listings from Selling Manager templates.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the template you are using to list an item.
								You can obtain a SaleTemplateID by calling GetSellingManagerInventory.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ScheduleTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Start time for the listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;Currently, only the
								following can be specified as children of this
								container: payment methods,
								the PayPal email address, and CategoryMappingAllowed. &lt;/b&gt;
								This container is intended for specifying
								item values that differ from values in the
								template specified in the SaleTemplateID field.
								However, currently, the only children that
								are allowed for this container are payment methods and
								a PayPal email address.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddItemFromSellingManagerTemplate -->
	<xs:element name="AddItemFromSellingManagerTemplateResponse" type="ns:AddItemFromSellingManagerTemplateResponseType"/>
	<xs:complexType name="AddItemFromSellingManagerTemplateResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns values indicating information for a new listing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier for the listing that was created by the 
								AddItemFromSellingManagerTemplate request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Start time for the listing that was created by the 
								AddItemFromSellingManagerTemplate request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								End time for the listing that was created by the 
								AddItemFromSellingManagerTemplate request. 
								This value is equal to the start time plus the listing duration.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the new item listing.
								The fees do not include the Final Value Fee (FVF), which cannot be determined
								until an item is sold.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the primary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID you passed in PrimaryCategory was mapped to a new ID by eBay.
								If the primary category has not changed or it has expired with no replacement,
								CategoryID does not return a value.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the secondary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID you passed in SecondaryCategory was mapped to a new ID by eBay.
								If the secondary category has not changed or it has expired with no replacement,
								Category2ID does not return a value.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>AddItemFromSellingManagerTemplate</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddItems -->
	<xs:element name="AddItemsRequest" type="ns:AddItemsRequestType"/>
	<xs:complexType name="AddItemsRequestType">
		<xs:annotation>
			<xs:documentation>
				Defines from one to five items and lists them on a specified eBay site.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddItem, AddToItemDescription, EndItems, GetItem, 
					GetSellerList, RelistItem, ReviseItem, VerifyAddItem
				</RelatedCalls>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ListingAnItem</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ListingItemsIntro</URL>
				</SeeLink>
				<SeeLink>
					<Title>Seller Checklist</Title>
					<URL>http://pages.ebay.com/sell/April2009Update/Checklist</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ConsideringBestMatch</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AddItemRequestContainer" type="ns:AddItemRequestContainerType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Defines a single item to be listed on eBay. This container is similar
								to an AddItem request. Up to five containers can be included
								in one AddItems request.
							</xs:documentation>
							<xs:appinfo>
								<MinOccurs>1</MinOccurs>
								<MaxOccurs>5</MaxOccurs>
								<CallInfo>
									<CallName>AddItems</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddItems -->
	<xs:element name="AddItemsResponse" type="ns:AddItemsResponseType"/>
	<xs:complexType name="AddItemsResponseType">
		<xs:annotation>
			<xs:documentation>
				The response of the &lt;b&gt;AddItems&lt;b&gt; call. The response includes the 
				Item IDs of the newly created listings, the eBay category each item is listed under, 
				the seller-defined SKUs of the items (if any), the listing recommendations for each item 
				(if applicable), the start and end time of each listing, and the estimated fees that
				each listing will incur.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AddItemResponseContainer" type="ns:AddItemResponseContainerType" minOccurs="0" maxOccurs="unbounded">
						 <xs:annotation>
							<xs:documentation>
								One &lt;b&gt;AddItemResponseContainer&lt;/b&gt; container is returned for each
								listing that is being created with the &lt;b&gt;AddItems&lt;/b&gt; call. Each
								container includes the &lt;b&gt;ItemID&lt;/b&gt; of each newly created listings,
								the eBay category each item is listed under, the seller-defined SKUs of the
								items (if any), the listing recommendations for each item (if applicable), the
								start and end time of each listing, and the estimated fees that each listing
								will incur.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddItems</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
					 	 </xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddMemberMessageAAQToPartner -->
	<xs:element name="AddMemberMessageAAQToPartnerRequest" type="ns:AddMemberMessageAAQToPartnerRequestType"/>
	<xs:complexType name="AddMemberMessageAAQToPartnerRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a buyer and seller in an order relationship to
				send messages to each other's My Messages Inboxes.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddMemberMessagesAAQToBidder, AddMemberMessageRTQ, DeleteMyMessages,
					GetMemberMessages, ReviseMyMessages, ReviseMyMessagesFolders
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique ID of the item about which the question was asked.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddMemberMessageAAQToPartner</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MemberMessage" type="ns:MemberMessageType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container for the message. Includes the message body, plus other values
								related to the message.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddMemberMessageAAQToPartner</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddMemberMessageAAQToPartner -->
	<xs:element name="AddMemberMessageAAQToPartnerResponse" type="ns:AddMemberMessageAAQToPartnerResponseType"/>
	<xs:complexType name="AddMemberMessageAAQToPartnerResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to AddMemberMessageAAQToPartner request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddMemberMessageRTQ -->
	<xs:element name="AddMemberMessageRTQRequest" type="ns:AddMemberMessageRTQRequestType"/>
	<xs:complexType name="AddMemberMessageRTQRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to reply to a question about an active item listing.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddMemberMessagesAAQToBidder, AddMemberMessageAAQToPartner, DeleteMyMessages,
					GetMemberMessages, GetMyMessages, ReviseMyMessages, ReviseMyMessagesFolders
				</RelatedCalls>
				<SeeLink>
					<Title>Communication Between Members</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CommunicationBetweenMembers</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique ID of the item about which the question was asked. This field
								is not required in the request, if the request includes a RecipientID
								in the MemberMessage container.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddMemberMessageRTQ</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MemberMessage" type="ns:MemberMessageType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container for the message. Includes the message body (which should answer
								the question that an eBay user asks you (the seller) about an active
								listing), plus other values related to the message.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddMemberMessageRTQ</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddMemberMessageRTQ -->
	<xs:element name="AddMemberMessageRTQResponse" type="ns:AddMemberMessageRTQResponseType"/>
	<xs:complexType name="AddMemberMessageRTQResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to AddMemberMessageRTQ request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddMemberMessagesAAQToBidder -->
	<xs:element name="AddMemberMessagesAAQToBidderRequest" type="ns:AddMemberMessagesAAQToBidderRequestType"/>
	<xs:complexType name="AddMemberMessagesAAQToBidderRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to send up to 10 messages to bidders, or to users who have
				made offers via Best Offer, regarding an active item listing.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddMemberMessageAAQToPartner, AddMemberMessageRTQ, DeleteMyMessages,
					GetMemberMessages, GetMyMessages, GetUserContactDetails, ReviseMyMessages,
					ReviseMyMessagesFolders
				</RelatedCalls>
				<SeeLink>
					<Title>Communication Between Members</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CommunicationBetweenMembers</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AddMemberMessagesAAQToBidderRequestContainer" type="ns:AddMemberMessagesAAQToBidderRequestContainerType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
							Allows a seller to send up to 10 messages to
							bidders and users who have made offers (via Best
							Offer) during an active listing.
							</xs:documentation>
							<xs:appinfo>
								<maxOccurs>10</maxOccurs>
								<CallInfo>
									<CallName>AddMemberMessagesAAQToBidder</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddMemberMessagesAAQToBidder -->
	<xs:element name="AddMemberMessagesAAQToBidderResponse" type="ns:AddMemberMessagesAAQToBidderResponseType"/>
	<xs:complexType name="AddMemberMessagesAAQToBidderResponseType">
		<xs:annotation>
			<xs:documentation>
				Type defining the &lt;b&gt;AddMemberMessagesAAQToBidderResponseContainer&lt;/b&gt; container, which consists 
				of the &lt;b&gt;Ack&lt;/b&gt; field (indicating the result of the send message operation) and the &lt;b&gt;CorrelationID&lt;/b&gt; 
				field (used to track multiple send message operations performed in one call).
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AddMemberMessagesAAQToBidderResponseContainer" type="ns:AddMemberMessagesAAQToBidderResponseContainerType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the &lt;b&gt;Ack&lt;/b&gt; field (indicating the result of the send message
								operation) and the &lt;b&gt;CorrelationID&lt;/b&gt; field (used to track multiple send
								message operations performed in one call).
							</xs:documentation>
							<xs:appinfo>
								<maxOccurs>10</maxOccurs>
								<CallInfo>
									<CallName>AddMemberMessagesAAQToBidder</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddOrder -->
	<xs:element name="AddOrderRequest" type="ns:AddOrderRequestType"/>
	<xs:complexType name="AddOrderRequestType">
		<xs:annotation>
			<xs:documentation>
				Combines two or more order line items into a single order, enabling a buyer to pay for all of those order line items with a single payment (and, if so arranged, ship all of the items together).
			</xs:documentation>
			<xs:appinfo>
			   <Summary>Combines two or more order line items into a single order, enabling a buyer to pay for all of those order line items with a single payment.
			   </Summary>
				<RelatedCalls>GetItemTransactions, GetOrders</RelatedCalls>
				<SeeLink>
					<Title>Reviewing and Modifying an Order Line Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CreatingaCombinedPaymentOrder</URL>
					<For>additional insight into prerequisites</For>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=WorkingWithCombinedPayment</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Order" type="ns:OrderType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The root container of the &lt;b&gt;AddOrder&lt;/b&gt; request. In this 
								call, the seller identifies two or more order line items from the same buyer 
								through the &lt;b&gt;TransactionArray&lt;/b&gt; container, specifies one or 
								more accepted payment methods through the &lt;b&gt;PaymentMethods&lt;/b&gt; 
								field(s), and specifies available shipping services and other shipping details 
								through the &lt;b&gt;ShippingDetails&lt;/b&gt; container.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddOrder</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddOrder -->
	<xs:element name="AddOrderResponse" type="ns:AddOrderResponseType"/>
	<xs:complexType name="AddOrderResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns a unique identifier for the order. A buyer may make a single
				payment to purchase all of the order line items included
				in the order.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="OrderID" type="ns:OrderIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier for the Combined Payment order. This OrderID can be used as an input filter in GetOrders. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddOrder</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CreatedTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The date and time the Combined Payment order was created.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddOrder</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddSecondChanceItem -->
	<xs:element name="AddSecondChanceItemRequest" type="ns:AddSecondChanceItemRequestType"/>
	<xs:complexType name="AddSecondChanceItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Creates a new Second Chance Offer (that is, an offer for an unsold item)
				for one of that item's non-winning bidders.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetAllBidders, VerifyAddSecondChanceItem</RelatedCalls>
				<SeeLink>
					<Title>Making Second Chance Offers for Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=MakingSecondChanceOffersForItems</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="RecipientBidderUserID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the bidder from the original, ended listing to whom the seller
								is extending the second chance offer. Specify only one
								RecipientBidderUserID per call. If multiple users are specified (each in a
								RecipientBidderUserID node), only the last one specified receives the
								offer.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSecondChanceItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BuyItNowPrice" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The amount the offer recipient must pay to purchase the item
								from the second chance offer listing. Use only when the original
								item was listed in an eBay Motors vehicle category (or in some
								categories on U.S. and international sites for
								high-priced items, such as items in many U.S. and Canada
								Business and Industrial categories) and it ended unsold
								because the reserve price was not met. Otherwise, eBay
								establishes the price and no price should be submitted.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSecondChanceItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Duration" type="ns:SecondChanceOfferDurationCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the length of time the second chance offer listing will be
								active. The recipient bidder has that much time to purchase the item or
								the listing expires.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSecondChanceItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the item ID for the original, ended listing from which the
								second chance offer item comes. A new ItemID is returned for the second
								chance offer item.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>AddSecondChanceItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerMessage" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Message content. Cannot contain HTML, asterisks, or quotes. This content
								is included in the second chance offer email sent to the recipient, which
								can be retrieved with GetMyMessages.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>1000</MaxLength>
								<CallInfo>
									<CallName>AddSecondChanceItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddSecondChanceItem -->
	<xs:element name="AddSecondChanceItemResponse" type="ns:AddSecondChanceItemResponseType"/>
	<xs:complexType name="AddSecondChanceItemResponseType">
		<xs:annotation>
			<xs:documentation>
				AddSecondChanceItem response for a new Second Chance Offer listing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the item ID for the new second chance
								offer listing. Different from the original ItemID passed in the request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>AddSecondChanceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the date and time when the the new second chance offer listing
								became active and the recipient user could purchase the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSecondChanceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the date and time when the second chance offer listing expires,
								at which time the listing ends (if the recipient user does not purchase
								the item first).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSecondChanceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddSellingManagerInventoryFolder -->
	<xs:element name="AddSellingManagerInventoryFolderRequest" type="ns:AddSellingManagerInventoryFolderRequestType"/>
<xs:complexType name="AddSellingManagerInventoryFolderRequestType">
		<xs:annotation>
			<xs:documentation>
			  Adds a new product folder to a user's Selling Manager account.
				This call is subject to change without notice; the deprecation process is
				inapplicable to this call.
		</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="FolderName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Name of the new Selling Manager inventory folder.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerInventoryFolder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ParentFolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Unique Folder ID of parent folder. If no ParentFolderID is submitted, Folder
								is added to root level.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerInventoryFolder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Comment" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Contains comments that will be associated with this folder.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerInventoryFolder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddSellingManagerInventoryFolder -->
	<xs:element name="AddSellingManagerInventoryFolderResponse" type="ns:AddSellingManagerInventoryFolderResponseType"/>
	<xs:complexType name="AddSellingManagerInventoryFolderResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of an add folder operation.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="FolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								New ID of the folder newly created in the user's Selling Manager account.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerInventoryFolder</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddSellingManagerProduct -->
	<xs:element name="AddSellingManagerProductRequest" type="ns:AddSellingManagerProductRequestType"/>
	<xs:complexType name="AddSellingManagerProductRequestType">
		<xs:annotation>
			<xs:documentation>
				Creates a Selling Manager product. Sellers use Selling Manager products to store SYI forms for use
				as listing templates.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Creates a Selling Manager product, which contains templates for repeat listings.
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates,AddSellingManagerInventoryFolder</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SellingManagerProductDetails" type="ns:SellingManagerProductDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains product information that the seller has recorded, such as a product
								description and inventory and restocking details.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerProduct</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Unique identifier of the folder. This ID is created when the folder is added and is returned by the
								AddSellingManagerInventoryFolder call.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerProduct</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingManagerProductSpecifics" type="ns:SellingManagerProductSpecificsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies an eBay category associated with the product,
								defines Item Specifics that are relevant to the product,
								and defines variations available for the product
								(which may be used to create mult-variation listings).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerProduct</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddSellingManagerProduct -->
	<xs:element name="AddSellingManagerProductResponse" type="ns:AddSellingManagerProductResponseType"/>
	<xs:complexType name="AddSellingManagerProductResponseType">
		<xs:annotation>
			<xs:documentation>
				Response for adding a Selling Manager product.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SellingManagerProductDetails" type="ns:SellingManagerProductDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The details of the product.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerProduct</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddSellingManagerTemplate -->
	<xs:element name="AddSellingManagerTemplateRequest" type="ns:AddSellingManagerTemplateRequestType"/>
	<xs:complexType name="AddSellingManagerTemplateRequestType">
		<xs:annotation>
			<xs:documentation>
				Adds a Selling Manager template.
				One product can have up to 20 templates associated with it.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the data in your template, i.e. the data needed to
								list an item. The item data you specify will be used
								when you list items from the template you are adding.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SaleTemplateName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The name you provide for the template. If you don't specify
								a name, then Item.Title is used as the name.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the product with which the template will be associated.
								Before calling AddSellingManagerTemplate, you can obtain a product ID
								from the response of an AddSellingManagerProduct call.
								That is, after you add a product using AddSellingManagerProduct, a product ID is
								returned in the SellingManagerProductDetails.ProductID field.
								The GetSellingManagerTemplates
								call also returns product IDs.
								Alternatively, you can obtain information about a user's existing
								products, including the product IDs, by calling GetSellingManagerInventory.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddSellingManagerTemplate -->
	<xs:element name="AddSellingManagerTemplateResponse" type="ns:AddSellingManagerTemplateResponseType"/>
	<xs:complexType name="AddSellingManagerTemplateResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains values indicating template information for a newly-exported item.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the primary category in which the item would be listed.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the secondary category (if any) in which the item would be listed.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the Selling Manager template. Store this value, for use in 
								other Selling Manager calls.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SaleTemplateGroupID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Ignore this value. For the output value that indicates the 
								ID of the product associated with the template, 
								use SellingManagerProductDetails.ProductID.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SaleTemplateName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The name of the template, as it will appear in Selling Manager Pro. 
								This name is the input value you provided in the SaleTemplateName field. 
								If you didn't specify a value for
								SaleTemplateName, then Item.Title is used as the name.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingManagerProductDetails" type="ns:SellingManagerProductDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The details of the product with which the template is associated.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the new listing template.
								Note that the fee will only be charged when an item is created from the template.
								The fees do not include the Final Value Fee (FVF), which cannot be determined
								until an item is sold.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>Final Value Fees and Credits</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FinalValueFeesAndCredits</URL>
								</SeeLink>
								<SeeLink>
									<Title>Fees per Site</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeesPerSite</URL>
								</SeeLink>
								<SeeLink>
									<Title>Using Feature Packs to Save on Upgrade Fees</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UsingFeaturePacks</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddToItemDescription -->
	<xs:element name="AddToItemDescriptionRequest" type="ns:AddToItemDescriptionRequestType"/>
	<xs:complexType name="AddToItemDescriptionRequestType">
		<xs:annotation>
			<xs:documentation>
				Appends a horizontal rule, then a message about what time the
				addition was made by the seller, and then the seller-specified text.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Changing Item Descriptions</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ChangingItemDescriptions</URL>
				</SeeLink>
				<RelatedCalls>AddItem, ReviseItem</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique item ID that identifies the target item listing, the description
								of which is appended with the text specified in Description.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>AddToItemDescription</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Description" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the text to append to the end of the listing's description.
								Text appended to a listing's description must abide by the rules
								applicable to this data (such as no JavaScript) as is the case when
								first listing the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddToItemDescription</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddToItemDescription -->
	<xs:element name="AddToItemDescriptionResponse" type="ns:AddToItemDescriptionResponseType"/>
	<xs:complexType name="AddToItemDescriptionResponseType">
		<xs:annotation>
			<xs:documentation>
				Indicates the success or failure of the attempt to add text to the end of the
				description section of an item listing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddToWatchList -->
	<xs:element name="AddToWatchListRequest" type="ns:AddToWatchListRequestType"/>
	<xs:complexType name="AddToWatchListRequestType">
		<xs:annotation>
			<xs:documentation>
				Adds one or more items to the user's My eBay watch list.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetMyeBayBuying, GetMyeBaySelling, RemoveFromWatchList</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The ItemID of the item that is to be added to the watch list.
								The item must be a currently active item, and the total number
								of items in the
								watchlist (after the items in the request have been added) cannot exceed
								the maximum allowed number of watch list items. One or more ItemID fields can be specified. A separate error node will be
								returned for each item that fails.&lt;br&gt;
								&lt;br&gt;
								Either ItemID or VariationKey is required
								(but do not pass in both).
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>AddToWatchList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
						<xs:element name="VariationKey" type="ns:VariationKeyType" minOccurs="0" maxOccurs="unbounded">
 					   <xs:annotation>
							<xs:documentation>
								A variation (or set of variations) that you want to watch.
								Use this to watch a particular variation (not the entire item).
								Either the top-level ItemID or VariationKey is required
								(but do not pass in both).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddToWatchList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddToWatchList -->
	<xs:element name="AddToWatchListResponse" type="ns:AddToWatchListResponseType"/>
	<xs:complexType name="AddToWatchListResponseType">
		<xs:annotation>
					<xs:documentation>
						Indicates the number of items currently in the user's Watch List and the maximum
						number of items allowed in the Watch List.
					</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="WatchListCount" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The number of items in the user's watch list (after those specified
								in the call request have been added)
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddToWatchList</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="WatchListMaximum" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The maximum number of items allowed in watch lists. Currently this
								value is the same for all sites and all users.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddToWatchList</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddTransactionConfirmationItem -->
	<xs:element name="AddTransactionConfirmationItemRequest" type="ns:AddTransactionConfirmationItemRequestType"/>
	<xs:complexType name="AddTransactionConfirmationItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Ends the eBay Motors listing specified by ItemID and creates a new Transaction
				Confirmation Request (TCR) for the item, thus enabling the TCR recipient to
				purchase the item. You can also use this call to see if a new TCR can be created
				for the specified item.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Ends the eBay Motors listing specified by ItemID and creates a new Transaction
					Confirmation Request (TCR) for the item, thus enabling the TCR recipient to
					purchase the item. You can also use this call to see if a new TCR can be created
					for the specified item.
				</Summary>
				<RelatedCalls>GetBestOffers, GetBidderList, GetItem, GetSellerList</RelatedCalls>
				<SeeLink>
					<Title>Learning About Bidders</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=LearningAboutBidders</URL>
				</SeeLink>
				<SeeLink>
					<Title>Enabling Best Offer</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EnablingBestOffer</URL>
				</SeeLink>
				<SeeLink>
					<Title>Communication Between Members</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CommunicationBetweenMembers</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="RecipientUserID" type="ns:UserIDType">
						<xs:annotation>
							<xs:documentation>
								Specifies the user to whom the seller is offering the Transaction
								Confirmation Request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VerifyEligibilityOnly" type="xs:string">
						<xs:annotation>
							<xs:documentation>
								If true, specifies that the seller is verifying whether a new Transaction
								Confirmation Request (TCR) can be created. Thus, if this value is passed
								as true, then no Transaction Confirmation Request is actually made. If
								VerifyEligibilityOnly is not passed, or is false, a Transaction
								Confirmation Request is actually made.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RecipientPostalCode" type="xs:string">
						<xs:annotation>
							<xs:documentation>
								Specifies the postal code of the user to whom the seller is offering the
								Transaction Confirmation Request. Required only if the user does not meet
								the other options listed in RecipientRelationCodeType. An error is
								returned if RecipientUserID and RecipientPostalCode do not match for more
								than 3 times for a seller per day.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RecipientRelationType" type="ns:RecipientRelationCodeType">
						<xs:annotation>
							<xs:documentation>
								Specifies the current relationship between the seller and the potential
								buyer. A seller can make a Transaction Confirmation Request (TCR) for an
								item to a potential buyer if the buyer meets one of several criteria. A
								TCR is sent by a seller to one of the following: a bidder, a best offer
								buyer, a member with an ASQ question, or any member with a postal code.
								See the values and annotations in RecipientRelationCodeType.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NegotiatedPrice" type="ns:AmountType">
						<xs:annotation>
							<xs:documentation>
								The amount the offer recipient must pay to buy the item
								specified in the Transaction Confirmation Request (TCR).
								A negotiated amount between the buyer and the seller.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingDuration" type="ns:SecondChanceOfferDurationCodeType">
						<xs:annotation>
							<xs:documentation>
								Specifies the length of time the item in the Transaction Confirmation
								Request (TCR) will be available for purchase.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType">
						<xs:annotation>
							<xs:documentation>
								The ItemID of the item that the seller wants to end in order to create a
								Transaction Confirmation Request (TCR).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Comments" type="xs:string">
						<xs:annotation>
							<xs:documentation>
								Comments the seller wants to send to the recipient (bidder, best offer
								buyer, member with an ASQ question, or member with a postal code).
     					</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: AddTransactionConfirmationItem -->
	<xs:element name="AddTransactionConfirmationItemResponse" type="ns:AddTransactionConfirmationItemResponseType"/>
	<xs:complexType name="AddTransactionConfirmationItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns an item ID for a new Transaction Confirmation Request (TCR).
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The new item ID for the item in the new Transaction Confirmation Request (TCR).
								This field is not returned if the request was only used to verify that a new TCR could be created.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The date and time when the item in the new Transaction Confirmation Request (TCR)
								becomes available for purchase.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The date and time when the item in the new Transaction Confirmation Request (TCR)
								is no longer available for purchase.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddTransactionConfirmationItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: CompleteSale -->
	<xs:element name="CompleteSaleRequest" type="ns:CompleteSaleRequestType"/>
	<xs:complexType name="CompleteSaleRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to do various tasks after the creation of a single line item or
				multiple line item order. Typically, this call is used after the
				buyer has paid for the order, but it can be called by the
				seller beforehand. Typical post-payment tasks available to this call include
				marking the order as paid, marking the order as shipped, providing shipment tracking
				details, and leaving feedback for the buyer.
			</xs:documentation>
			<xs:appinfo>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. An &lt;b&gt;ItemID&lt;/b&gt; can be paired up
								with a corresponding &lt;b&gt;TransactionID&lt;/b&gt; and used in the &lt;b&gt;CompleteSale&lt;/b&gt; request
								to identify a single line item order.
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;OrderLineItemID&lt;/b&gt; is used to identify a single line item order,
								or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line item
								 order, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair must be
								specified. For a multiple line item order, &lt;b&gt;OrderID&lt;/b&gt;
								must be used. If &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; are specified, the
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is ignored if present in the same request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs
								are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay order line item (transaction). The
								&lt;b&gt;TransactionID&lt;/b&gt; can be paired up with the corresponding &lt;b&gt;ItemID&lt;/b&gt; and used in
								the &lt;b&gt;CompleteSale&lt;/b&gt; request to identify a single line item order.
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;OrderLineItemID&lt;/b&gt; is used to identify a single line item order,
								or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line item
								 order, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair must be
								specified. For a multiple line item order, &lt;b&gt;OrderID&lt;/b&gt;
								must be used. If &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; are specified, the
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is ignored if present in the same request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FeedbackInfo" type="ns:FeedbackInfoType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container is used by the seller to leave feedback for the buyer for the
								order line item identified in the call request. The seller must include and
								specify all fields of this type, including the buyer's eBay User ID, the
								Feedback rating (a seller can only leave a buyer a "Positive" rating), and a
								comment, which helps justify the Feedback rating. The eBay User ID must match 
								the buyer who bought the order line item, or an error will occur. An error will 
								also occur if Feedback has already been left for the buyer (either through API 
								or the Web flow).
								&lt;br&gt;&lt;br&gt;
								To determine if Feedback has already been left for an order line item, you can 
								call &lt;b class="con"&gt;GetFeedback&lt;/b&gt;, passing in the 
								&lt;b class="con"&gt;OrderLineItemID&lt;/b&gt; value in the call request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Shipped" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The seller includes and sets this field to true if the order has been
								shipped. If the call is successful, the order line item(s) are marked as
								Shipped in My eBay.
								&lt;br&gt;&lt;br&gt;
								If the seller includes and sets this field to false, the order line item(s)
								are marked (or remain) as Not Shipped in My eBay.
								&lt;br&gt;&lt;br&gt;
								If this field is not included, the shipped status of the order line
								item(s) remain unchanged in My eBay.
								&lt;br&gt;&lt;br&gt;
								If shipment tracking information is provided for an order line item through
								the Shipment container in the same request, the order line item is marked as
								shipped automatically and the &lt;b&gt;Shipped&lt;/b&gt; field is not
								required.
								<!-- &lt;br&gt;&lt;br&gt;
								For orders going through the new payment process, DE and AT sellers mark an 
								order as shipped to expedite the seller payout process. -->
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Paid" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The seller includes and sets this field to true if the buyer has paid for
								the order. If the call is successful, the
								order line item(s) are marked as Paid in My eBay.
								&lt;br&gt;&lt;br&gt;
								If the seller includes and sets this field to false, the order line item(s)
								are marked (or remain) as Not Paid in My eBay.
								&lt;br&gt;&lt;br&gt;
								If this field is not included, the paid status of the order line
								item(s) remain unchanged in My eBay.
								<!-- &lt;br&gt;&lt;br&gt;
								If an order is going through the new eBay payment process, DE and AT sellers
								cannot use this field to mark the order as paid, as this can only be
								done by eBay. -->
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingType" type="ns:ListingTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field is required if &lt;b&gt;CompleteSale&lt;/b&gt; is being used for a Half.com
								order. The value should be set to &lt;i&gt;Half&lt;/i&gt;, which is the only applicable
								&lt;b&gt;ListingType&lt;/b&gt; value for this call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<OnlyTheseValues>Half</OnlyTheseValues>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Shipment" type="ns:ShipmentType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of shipment tracking information, shipped time, and an
								optional text field to provide additional details to the buyer. Setting the
								tracking number and shipping carrier automatically marks the item as shipped
								and the &lt;b&gt;Shipped&lt;/b&gt; field is not required.
								&lt;br&gt;&lt;br&gt;
								(If you supply &lt;b&gt;ShipmentTrackingNumber&lt;/b&gt; you must also supply 
								&lt;b&gt;ShippingCarrierUsed&lt;/b&gt;, otherwise you will get an error.
								&lt;br&gt;&lt;br&gt;
								To modify the shipping tracking number and/or carrier, supply the new number
								in &lt;b&gt;ShipmentTrackingNumber&lt;/b&gt; or supply the value for
								&lt;b&gt;ShippingCarrierUsed&lt;/b&gt; or both. The old number and carrier
								are deleted and the new ones are added.
								&lt;br&gt;&lt;br&gt;
								To simply delete the current tracking details altogether, supply empty
								&lt;b&gt;Shipment&lt;/b&gt; tags.
								&lt;br&gt; 
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								Top-Rated sellers must have a record of uploading shipment tracking
								information (through site or through API) for at least 90 percent of their order line
								items (purchased by U.S. buyers) to keep their status as Top-Rated sellers. For more
								information on the requirements to becoming a Top-Rated Seller, see the 
								&lt;a href="http://pages.ebay.com/help/sell/top-rated.html"&gt;Becoming a Top-Rated Seller and qualifying for Top-Rated Plus&lt;/a&gt; 
								customer support page.
								&lt;/span&gt;
							&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier that identifies a single line item or multiple line
								item order. 
								&lt;br&gt;&lt;br&gt; 
								For a single line item order, the &lt;b&gt;OrderID&lt;/b&gt; value is identical to the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value that is generated upon creation of the order line
								item. For multiple line item orders, the &lt;b&gt;OrderID&lt;/b&gt; value is created by eBay
								when the buyer is purchasing multiple order line items from the same seller at the same time.
								For multiple line item orders not going through the eBay Cart flow, a Combined Payment order can be created by the seller
								through the &lt;b&gt;AddOrder&lt;/b&gt; call. The &lt;b&gt;OrderID&lt;/b&gt; can be used in the &lt;b&gt;CompleteSale&lt;/b&gt;
								request to identify a single or multiple line item order.
								&lt;br&gt;&lt;br&gt;
								&lt;b&gt;OrderID&lt;/b&gt; overrides an &lt;b&gt;OrderLineItemID&lt;/b&gt; or &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair if
								these fields are also specified in the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier for an eBay order line item and
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. For a single line item order, the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value can be passed into the &lt;b&gt;OrderID&lt;/b&gt; field in the
								&lt;b&gt;CompleteSale&lt;/b&gt; request.
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is used to identify a single line
								item order, or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line
								item order, the &lt;b&gt;OrderLineItemID&lt;/b&gt; must be specified.
								For a multiple line item order, &lt;b&gt;OrderID&lt;/b&gt; must be
								used. If &lt;b&gt;OrderLineItemID&lt;/b&gt; is specified, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair are
								ignored if present in the same request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50 (Note: ItemIDs and TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>CompleteSale</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: CompleteSale -->
	<xs:element name="CompleteSaleResponse" type="ns:CompleteSaleResponseType"/>
	<xs:complexType name="CompleteSaleResponseType">
		<xs:annotation>
			<xs:documentation>
			Indicates the success or failure of the attempt to leave feedback for the buyer,
			change the paid status in My eBay, and/or change the shipped status in My eBay.
			&lt;br&gt;&lt;br&gt;
			Applies to half.com.
			&lt;br&gt;&lt;br&gt;
			&lt;br&gt;&lt;br&gt;
			When CompleteSale is applied to a specified order (by specifying OrderID), it
			also applies to the child transactions associated with the order. An OrderID
			cannot be used with half.com items.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ConfirmIdentity -->
	<xs:element name="ConfirmIdentityRequest" type="ns:ConfirmIdentityRequestType"/>
	<xs:complexType name="ConfirmIdentityRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns the ID of a user who has gone through an application's consent flow
				process for obtaining an authorization token.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>FetchToken, GetSessionID, GetTokenStatus, RevokeToken</RelatedCalls>
				<SeeLink>
					<Title>Getting Tokens</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingAToken</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SessionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A string obtained by making a GetSessionID call, passed in redirect
								URL to the eBay signin page.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ConfirmIdentity</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ConfirmIdentity -->
	<xs:element name="ConfirmIdentityResponse" type="ns:ConfirmIdentityResponseType"/>
	<xs:complexType name="ConfirmIdentityResponseType">
		<xs:annotation>
			<xs:documentation>
				Confirms the identity of the user by returning the UserID and the EIASToken belonging to
				the user.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="UserID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique eBay user ID for the user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ConfirmIdentity</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteMyMessages -->
	<xs:element name="DeleteMyMessagesRequest" type="ns:DeleteMyMessagesRequestType" />
	<xs:complexType name="DeleteMyMessagesRequestType">
		<xs:annotation>
			<xs:documentation>
				Removes selected messages for a given user.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddMemberMessagesAAQToBidder, AddMemberMessageRTQ, GetMemberMessages,
					GetMyMessages, ReviseMyMessages, ReviseMyMessagesFolders
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AlertIDs" type="ns:MyMessagesAlertIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field will be deprecated in an upcoming release. This field formerly
								contained a list of up to 10 AlertID values.
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
					<!-- <CallInfo>
									<CallName>DeleteMyMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo> -->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MessageIDs" type="ns:MyMessagesMessageIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains a list of up to 10 MessageID values.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteMyMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteMyMessages -->
	<xs:element name="DeleteMyMessagesResponse" type="ns:DeleteMyMessagesResponseType"/>
	<xs:complexType name="DeleteMyMessagesResponseType">
		<xs:annotation>
			<xs:documentation>
				The response to DeleteMyMessagesRequestType. If the request was successful, 
				DeleteMyMessages returns nothing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerInventoryFolder -->
	<xs:element name="DeleteSellingManagerInventoryFolderRequest" type="ns:DeleteSellingManagerInventoryFolderRequestType"/>
	<xs:complexType name="DeleteSellingManagerInventoryFolderRequestType">
		<xs:annotation>
			<xs:documentation>
				Removes an inventory folder when a user deletes it in My eBay.
				This call is subject to change without notice; the deprecation process is inapplicable
				to this call.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Removes a Selling Manager inventory folder.
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="FolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Unique ID of the folder to be deleted.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerInventoryFolder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerInventoryFolder -->
	<xs:element name="DeleteSellingManagerInventoryFolderResponse" type="ns:DeleteSellingManagerInventoryFolderResponseType"/>
	<xs:complexType name="DeleteSellingManagerInventoryFolderResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of delete folder operation.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerItemAutomationRule -->
	<xs:element name="DeleteSellingManagerItemAutomationRuleRequest" type="ns:DeleteSellingManagerItemAutomationRuleRequestType">
	</xs:element>
	<xs:complexType name="DeleteSellingManagerItemAutomationRuleRequestType">
		<xs:annotation>
			<xs:documentation>
				Removes the association of Selling Manager automation rules
				to an item. Returns the remaining rules in the response.
				&lt;br&gt;&lt;br&gt;
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the item from which to delete automation rules.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerItemAutomationRule</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeleteAutomatedRelistingRule" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the automated relisting rules are removed from the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerItemAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeleteAutomatedSecondChanceOfferRule" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the automated second chance offer rule is removed from the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerItemAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
							</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerItemAutomationRule -->
	<xs:element name="DeleteSellingManagerItemAutomationRuleResponse" type="ns:DeleteSellingManagerItemAutomationRuleResponseType"/>
	<xs:complexType name="DeleteSellingManagerItemAutomationRuleResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the set of automation rules associated with the specified item.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AutomatedListingRule" type="ns:SellingManagerAutoListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the remaining automated listing rules associated with this item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedRelistingRule" type="ns:SellingManagerAutoRelistType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the remaining automated relisting rules associated with this item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedSecondChanceOfferRule" type="ns:SellingManagerAutoSecondChanceOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the remaining automated second chance offer rule associated with this item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains fees that may be incurred when items are listed using the 
								automation rules (e.g., a scheduled listing fee). Use of an automation rule 
								does not in itself have a fee, but use can result in a fee.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerProduct -->
	<xs:element name="DeleteSellingManagerProductRequest" type="ns:DeleteSellingManagerProductRequestType"/>
	<xs:complexType name="DeleteSellingManagerProductRequestType">
		<xs:annotation>
			<xs:documentation>
				Deletes a Selling Manager product.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ProductID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the product to be deleted.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerProduct</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerProduct -->
	<xs:element name="DeleteSellingManagerProductResponse" type="ns:DeleteSellingManagerProductResponseType"/>
	<xs:complexType name="DeleteSellingManagerProductResponseType">
		<xs:annotation>
			<xs:documentation>
				Response for deleting a Selling Manager product.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="DeletedSellingManagerProductDetails" type="ns:SellingManagerProductDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The details of the product.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerProduct</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerTemplate -->
	<xs:element name="DeleteSellingManagerTemplateRequest" type="ns:DeleteSellingManagerTemplateRequestType"/>
	<xs:complexType name="DeleteSellingManagerTemplateRequestType">
		<xs:annotation>
			<xs:documentation>
				Deletes a Selling Manager template.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the template to be deleted.
								You can obtain a SaleTemplateID by calling GetSellingManagerInventory.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplate</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerTemplate -->
	<xs:element name="DeleteSellingManagerTemplateResponse" type="ns:DeleteSellingManagerTemplateResponseType"/>
	<xs:complexType name="DeleteSellingManagerTemplateResponseType">
		<xs:annotation>
			<xs:documentation>
				Response for deleting a Selling Manager template.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="DeletedSaleTemplateID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedSaleTemplateName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The name of the Selling Manager template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerTemplateAutomationRule -->
	<xs:element name="DeleteSellingManagerTemplateAutomationRuleRequest" type="ns:DeleteSellingManagerTemplateAutomationRuleRequestType">
	</xs:element>
	<xs:complexType name="DeleteSellingManagerTemplateAutomationRuleRequestType">
		<xs:annotation>
			<xs:documentation>
				Removes the association of Selling Manager automation rules
				to a template. Returns the remaining rules in the response.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates,SetSellingManagerTemplateAutomationRule</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the template from which you want to remove automation rules.
								You can obtain a SaleTemplateID by calling GetSellingManagerInventory.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeleteAutomatedListingRule" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the automated listing rules are removed from the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeleteAutomatedRelistingRule" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the automated relisting rules are removed from the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeleteAutomatedSecondChanceOfferRule" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the automated second chance offer rule is removed from the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DeleteSellingManagerTemplateAutomationRule -->
	<xs:element name="DeleteSellingManagerTemplateAutomationRuleResponse" type="ns:DeleteSellingManagerTemplateAutomationRuleResponseType"/>
	<xs:complexType name="DeleteSellingManagerTemplateAutomationRuleResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the set of automation rules associated with the specified template.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AutomatedListingRule" type="ns:SellingManagerAutoListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the remaining automated listing rules associated with this template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedRelistingRule" type="ns:SellingManagerAutoRelistType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the remaining automated relisting rules associated with this template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedSecondChanceOfferRule" type="ns:SellingManagerAutoSecondChanceOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the remaining automated second chance offer rule associated with this template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains fees that may be incurred when items are listed using the 
								automation rules (e.g., a scheduled listing fee). Use of an automation rule 
								does not in itself have a fee, but use can result in a fee.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DeleteSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DisableUnpaidItemAssistance -->
	<xs:element name="DisableUnpaidItemAssistanceRequest" type="ns:DisableUnpaidItemAssistanceRequestType"/>
	<xs:complexType name="DisableUnpaidItemAssistanceRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller who has opted into the automated Unpaid Item Assistant
				mechanism to disable the Unpaid Item Assistant at the order line item
				level. This call can be made whether or not a Unpaid Item dispute
				exists for the order line item. If a dispute has already been created by the
				Unpaid Item Assistant, it is converted to a "manual" dispute for the seller to
				manage like any other manually-created dispute.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<URL>http://pages.ebay.com/sell/UPI/upiassistant/index.html</URL>
					<Title>Unpaid Item Assistant</Title>
				</SeeLink>
				<SeeLink>
					<URL>http://pages.ebay.com/sell/UPI/standardprocess/index.html</URL>
					<Title>Understanding the New Unpaid Item Process</Title>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. A listing can have multiple
								order line items (transactions), but only one &lt;b&gt;ItemID&lt;/b&gt;. To identify a
								specific order line item for which to disable the Unpaid Item Assistant
								mechanism, either an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair, an &lt;b&gt;OrderLineItemID&lt;/b&gt;, or a
								&lt;b&gt;DisputeID&lt;/b&gt; (if a dispute record already exists) is required in the request. 
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>DisableUnpaidItemAssistance</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of an order line item (transaction). An order line
								item is created once there is a commitment from a buyer to
								purchase an item. To identify a specific order line item for which to
								disable the Unpaid Item Assistant mechanism, either an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt;
								pair, an &lt;b&gt;OrderLineItemID&lt;/b&gt;, or a &lt;b&gt;DisputeID&lt;/b&gt; (if a dispute record already
								exists) is required in the request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>DisableUnpaidItemAssistance</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DisputeID" type="ns:DisputeIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for an Unpaid Item dispute. Any order line item can
								only have one dispute record, so &lt;b&gt;DisputeID&lt;/b&gt; can be used in the request to
								identify a specific order line item. If an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair or an
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is used to identify an order line item, &lt;b&gt;DisputeID&lt;/b&gt; cannot be used and will be ignored if it is included in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>DisableUnpaidItemAssistance</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier for an eBay order line item and is
							based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a hyphen in
							between these two IDs. To identify a specific order line item for which to
							disable the Unpaid Item Assistant mechanism, either an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt;
							pair, an &lt;b&gt;OrderLineItemID&lt;/b&gt;, or a &lt;b&gt;DisputeID&lt;/b&gt; is required in the request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>100</MaxLength>
								<CallInfo>
									<CallName>DisableUnpaidItemAssistance</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: DisableUnpaidItemAssistance -->
	<xs:element name="DisableUnpaidItemAssistanceResponse" type="ns:DisableUnpaidItemAssistanceResponseType"/>
	<xs:complexType name="DisableUnpaidItemAssistanceResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to DisableUnpaidItemAssistance request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: EndFixedPriceItem -->
	<xs:element name="EndFixedPriceItemRequest" type="ns:EndFixedPriceItemRequestType"/>
	<xs:complexType name="EndFixedPriceItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Ends the specified fixed-price listing before the date and time at which
				it would normally end (per the listing duration).
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>EndItem, RelistFixedPriceItem</RelatedCalls>
				<SeeLink>
					<Title>Ending Items Early</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EndingItemsEarly</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique item ID that identifies the item listing that you want to end.
								&lt;br&gt;&lt;br&gt;
								In the EndFixedPriceItem request, either ItemID or SKU is required.
								If both are passed in and they don't refer to the same listing, eBay
								ignores SKU and considers only the ItemID.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>EndFixedPriceItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndingReason" type="ns:EndReasonCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the seller's reason for ending the listing early. This field
								is required if the seller is ending the item early and the item did
								not successfully sell.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>EndFixedPriceItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique SKU of the item being ended. A SKU (stock keeping unit) is
								an identifier defined by a seller. SKU can only be used to end an
								item if you listed the item by using AddFixedPriceItem or
								RelistFixedPriceItem, and you set Item.InventoryTrackingMethod to SKU
								at the time the item was listed. (These criteria are necessary to
								uniquely identify the listing by a SKU.)
								&lt;br&gt;&lt;br&gt;
								In the EndFixedPriceItem request, either ItemID or SKU is required. If
								both are passed in and they don't refer to the same listing, eBay
								ignores SKU and considers only the ItemID.
								&lt;br&gt;&lt;br&gt;
								To remove a SKU when you revise or relist an item, use DeletedField in
								the revision or relist call.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50</MaxLength>
								<CallInfo>
									<CallName>EndFixedPriceItem</CallName>e>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: EndFixedPriceItem -->
	<xs:element name="EndFixedPriceItemResponse" type="ns:EndFixedPriceItemResponseType"/>
	<xs:complexType name="EndFixedPriceItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Acknowledgement that includes SKU, as well as the date and time the auction was
				ended due to the call to EndFixedPriceItem.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Timestamp that indicates the date and time (GMT) that the specified item listing
								was ended.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>EndFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If a SKU (stock-keeping unit) exists for the item listing, it is returned in
								the response.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50</MaxLength>
								<CallInfo>
									<CallName>EndFixedPriceItem</CallName>e>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: EndItem -->
	<xs:element name="EndItemRequest" type="ns:EndItemRequestType"/>
	<xs:complexType name="EndItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Ends the specified item listing before the date and time at which it would normally end per the listing duration.&amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddItem, EndFixedPriceItem, EndItems, RelistItem</RelatedCalls>
				<SeeLink>
					<Title>Ending Items Early</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EndingItemsEarly</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique item ID that identifies the item listing to end.
								&lt;br&gt;&lt;br&gt;
								For Half.com listings, you can either specify ItemID or
								SellerInventoryID.
								&lt;br&gt;&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>EndItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndingReason" type="ns:EndReasonCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the seller's reason for ending the listing early.
								This field is required if the seller is ending the item early and
								the item did not successfully sell.
								&lt;br&gt;&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>EndItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerInventoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier that the seller specified when they listed the
								Half.com item. For Half.com items, you can either specify ItemID or
								SellerInventoryID. If you specify both ItemID and SellerInventoryID,
								they must be for the same item (otherwise an error will occur).
								&lt;br&gt;&lt;br&gt;
								Applicable only to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>EndItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: EndItem -->
	<xs:element name="EndItemResponse" type="ns:EndItemResponseType"/>
	<xs:complexType name="EndItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Includes the acknowledgement of date and time the auction was
				ended due to the call to EndItem.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the date and time (returned in GMT) the specified item listing
								was ended.
								Also applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>EndItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: EndItems -->
	<xs:element name="EndItemsRequest" type="ns:EndItemsRequestType"/>
	<xs:complexType name="EndItemsRequestType">
		<xs:annotation>
			<xs:documentation>
				Ends up to 10 specified item listings before the date and time at which it would normally end per the listing duration.&amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddItems, EndItem, RelistItem</RelatedCalls>
				<SeeLink>
					<Title>Ending Items Early</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EndingItemsEarly</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="EndItemRequestContainer" type="ns:EndItemRequestContainerType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								A single container for an end item request. Multiple containers should be used to end multiple items. Up to ten (10) containers can  be included
								per a given EndItems request.
							</xs:documentation>
							<xs:appinfo>
								<MaxOccurs>10</MaxOccurs>
								<CallInfo>
									<CallName>EndItems</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: EndItems -->
	<xs:element name="EndItemsResponse" type="ns:EndItemsResponseType"/>
	<xs:complexType name="EndItemsResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains a response of the resulting status of ending each item.				
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="EndItemResponseContainer" type="ns:EndItemResponseContainerType" minOccurs="0" maxOccurs="unbounded">
						 <xs:annotation>
							<xs:documentation>
								Returns a response for an individually ended item. Mutiple containers will be listed if multiple items are ended.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>EndItems</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element> 
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ExtendSiteHostedPictures -->
	<xs:element name="ExtendSiteHostedPicturesRequest" type="ns:ExtendSiteHostedPicturesRequestType"/>
	<xs:complexType name="ExtendSiteHostedPicturesRequestType">
		<xs:annotation>
			<xs:documentation>
				Gives approved sellers the ability to extend the default and
				ongoing lifetime of pictures uploaded to eBay.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					UploadSiteHostedPictures
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="PictureURL" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The URL of the image hosted by eBay Picture Services.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ExtendSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExtensionInDays" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The number of days by which to extend the expiration date for the
								specified image.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ExtendSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ExtendSiteHostedPictures -->
	<xs:element name="ExtendSiteHostedPicturesResponse" type="ns:ExtendSiteHostedPicturesResponseType"/>
	<xs:complexType name="ExtendSiteHostedPicturesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the URL of an eBay Picture Services image whose expiration date was
				extended.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PictureURL" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The URL of the image in eBay Picture Services whose expiration date was
								extended.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ExtendSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: FetchToken -->
	<xs:element name="FetchTokenRequest" type="ns:FetchTokenRequestType"/>
	<xs:complexType name="FetchTokenRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves an authentication token for a user.&amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>ConfirmIdentity, GetSessionID, GetTokenStatus, RevokeToken</RelatedCalls>
				<SeeLink>
					<Title>Getting Tokens</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingAToken</URL>
				</SeeLink>
				<SeeLink>
					<Title>Getting Tokens for Applications with Multiple Users</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingATokenViaFetchToken</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SecretID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A value associated with the token retrieval request. SecretID is
								defined by the application, and is passed in the redirect URL to the
								eBay sign-in page. eBay recommends using a UUID for the secret ID
								value. You must also set Username (part of the RequesterCredentials)
								for the particular user of interest. SecretID and Username are not
								required if SessionID is present.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>FetchToken</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SessionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A value associated with the token retrieval request. eBay generates the
								session ID when the application makes a GetSessionID request. SessionID
								is passed in the redirect URL to the eBay sign-in page. The advantage
								of using SessionID is that it does not require UserID as part of the
								FetchToken request. SessionID is not required if SecretID is present.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>FetchToken</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: FetchToken -->
	<xs:element name="FetchTokenResponse" type="ns:FetchTokenResponseType"/>
	<xs:complexType name="FetchTokenResponseType">
		<xs:annotation>
			<xs:documentation>
				Includes the authentication token for the user and the date it expires.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="eBayAuthToken" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The authentication token for the user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>FetchToken</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>Getting Tokens</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingAToken</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HardExpirationTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time at which the token returned in eBayAuthToken expires
								and can no longer be used to authenticate the user for that application.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>FetchToken</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RESTToken" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The REST authentication token for the user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>FetchToken</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAccount -->
	<xs:element name="GetAccountRequest" type="ns:GetAccountRequestType"/>
	<xs:complexType name="GetAccountRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns a seller's invoice data for their eBay account, including the account's
				summary data.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetSellerDashboard, GetUser</RelatedCalls>
				<SeeLink>
					<Title>Getting Account Information</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingAccountInformation</URL>
				</SeeLink>
				<SeeLink>
					<Title>Testing Applications</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=TestingApps</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AccountHistorySelection" type="ns:AccountHistorySelectionCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the report format in which to return account entries.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="InvoiceDate" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the month and year of the invoice requested. The report includes
								only the entries that appear on the seller's invoice in the specified month
								and year. An entry can occur in one month and appear on the next month's
								invoice. Used with SpecifiedInvoice reports.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BeginDate" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the beginning of a date range during which a credit or debit
								occurred. Used when AccountHistorySelection is BetweenSpecifiedDates. Value
								must be less than or equal to the value specified in EndDate. The allowed
								date formats are YYYY-MM-DD and YYYY-MM-DD HH:mm:ss. You can retrieve
								information that is up to 4 months old.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndDate" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the end of a date range during which a credit or debit occurred.
								Used when AccountHistorySelection is BetweenSpecifiedDates. Value must be
								greater than or equal to the value specified in BeginDate. The allowed date
								formats are YYYY-MM-DD and YYYY-MM-DD HH:mm:ss.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Controls pagination of the response. For this request, the valid values of
								Pagination.EntriesPerPage are 0 to 2000, with a default of 500.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExcludeBalance" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether to calculate balances. Default is false, which calculates
								balances. The value true means do not calculate balances. If true,
								AccountEntry.Balance and AccountSummary.CurrentBalance are never returned
								in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExcludeSummary" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether to return account summary information in an
								AccountSummary node. Default is true, to return AccountSummary.
						  </xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeConversionRate" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether to retrieve the rate used for the currency conversion for usage transactions.
						  </xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AccountEntrySortType" type="ns:AccountEntrySortTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies how account entries should be sorted in the response, by an
								element and then in ascending or descending order.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Currency" type="ns:CurrencyCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the currency used in the account report. Do not specify Currency
								in the request unless the following conditions are met. First, the user has
								or had multiple accounts under the same UserID. Second, the account
								identified in the request uses the currency you specify in the request. An
								error is returned if no account is found that uses the currency you specify
								in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the item ID for which to return account entries. If ItemID is
								used, all other filters in the request are ignored. If the specified item
								does not exist or if the requesting user is not the seller of the item, an
								error is returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAccount -->
	<xs:element name="GetAccountResponse" type="ns:GetAccountResponseType"/>
	<xs:complexType name="GetAccountResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns information about an eBay seller's own account.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AccountID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the seller's unique account number.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AccountSummary" type="ns:AccountSummaryType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains summary data for the seller's account, such as the overall
								balance, bank account and credit card information, and amount and
								date of any past due balances. Can also contain data for
								one or more additional accounts, if the user has changed country
								of residence.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Currency" type="ns:CurrencyCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the currency used for monetary amounts in the report.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AccountEntries" type="ns:AccountEntriesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains individual account entries, according to the report's scope and date range.
								Each account entry represents one credit, debit, or administrative account action.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the total number of pages (TotalNumberOfPages) and the total
								number of account entries (TotalNumberOfEntries) that can be returned
								on repeated calls with the same format and report criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMoreEntries" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether there are more items yet to be retrieved. Additional calls
								must be made to retrieve those items.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EntriesPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the number of items that are being returned per virtual page of date.
								Value is the same as that specified in Pagination.EntriesPerPage.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates which page of data was just returned. Value is the same as the value
								specified in Pagination.PageNumber. If PageNumber in the request is higher than
								the total number of pages, the call fails with an error.)
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAccount</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAdFormatLeads -->
	<xs:element name="GetAdFormatLeadsRequest" type="ns:GetAdFormatLeadsRequestType"/>
	<xs:complexType name="GetAdFormatLeadsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves sales lead information for a lead generation listing.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of an item listed on the eBay site.
								Returned by eBay when the item is created. This ID must correspond
								to an ad format item.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetAdFormatLeads</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Status" type="ns:MessageStatusTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Filters the leads based on their status.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAdFormatLeads</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeMemberMessages" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Boolean which indicates whether to return mail messages for this lead in a MemberMessage node.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAdFormatLeads</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartCreationTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Used with EndCreationTime to limit the returned leads for a user to only
								those with a creation date greater than or equal to the specified date and
								time.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAdFormatLeads</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndCreationTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Used with StartCreationTime to limit the returned leads for a user to only
								those with a creation date less than or equal to the specified date and
								time.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAdFormatLeads</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAdFormatLeads -->
	<xs:element name="GetAdFormatLeadsResponse" type="ns:GetAdFormatLeadsResponseType"/>
	<xs:complexType name="GetAdFormatLeadsResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns number of leads and contact and other information for each lead. One
				AdFormatLead node is returned for each lead.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AdFormatLead" type="ns:AdFormatLeadType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Contains contact and other information for one lead. One node is
								returned for each lead. Only returned at a detail level of ReturnAll. At
								least one lead must be available for the specified item to return
								AdFormatLead.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAdFormatLeads</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AdFormatLeadCount" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The total number of leads returned. Only returned if you do not
								specify a detail level.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAdFormatLeads</CallName>
									<Details>DetailLevel: none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAllBidders -->
	<xs:element name="GetAllBiddersRequest" type="ns:GetAllBiddersRequestType"/>
	<xs:complexType name="GetAllBiddersRequestType">
		<xs:annotation>
			<xs:documentation>
				Provides three modes for retrieving a list of the users that bid on
				a listing.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSecondChanceItem</RelatedCalls>
				<SeeLink>
					<Title>Making Second Chance Offers for Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ExtendingSecondChanceOffer</URL>
					<For>detailed information on working with the result set.</For>
				</SeeLink>
				<SeeLink>
					<Title>Making Second Chance Offers for Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=MakingSecondChanceOffersForItems</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the item. The bidders who bid on this item are returned.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetAllBidders</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CallMode" type="ns:GetAllBiddersModeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies which bidder information to return.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAllBidders</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeBiddingSummary" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether return BiddingSummary container for each offer.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAllBidders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAllBidders -->
	<xs:element name="GetAllBiddersResponse" type="ns:GetAllBiddersResponseType"/>
	<xs:complexType name="GetAllBiddersResponseType">
		<xs:annotation>
			<xs:documentation>
				Includes the list of bidders for the requested item as part of the general item listing data. Some bidder information is anonymous, to protect bidders from fraud. If the seller makes this API call, the actual ids of all bidders on the seller's item will be returned. If a bidder makes this API call, the bidder's actual id will be returned. Information for all competing bidders or outside watchers will be returned as anonymized userIDs. See See &lt;a href="http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=AnonymousUserInfo"&gt;Working with Anonymous User Information&lt;/a&gt;in the eBay Web Services Guide for more information.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="BidArray" type="ns:OfferArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains a list of OfferType objects. Each
								OfferType object represents the data for one bidder and bid.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAllBidders</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HighBidder" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								eBay user ID for the user with the highest bid (or the earliest timestamp, in the event of a tie); a second chance offer candidate.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAllBidders</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HighestBid" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Bid amount offered by the HighBidder.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAllBidders</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingStatus" type="ns:ListingStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies an active or ended listing's status in eBay's processing workflow.
								If a listing ends with a sale (or sales), eBay needs to update the sale details (e.g., winning bidder) and other information. This processing
								can take several minutes. If you retrieve a sold item, use this listing status information to determine whether eBay has finished processing the listing so that you can be sure the winning bidder and other details are correct and complete.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetAllBidders</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetApiAccessRules -->
	<xs:element name="GetApiAccessRulesRequest" type="ns:GetApiAccessRulesRequestType"/>
	<xs:complexType name="GetApiAccessRulesRequestType">
		<xs:annotation>
			<xs:documentation>
				Reports how many calls your application has made and is allowed to make per hour or day.&amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<URL>http://developer.ebay.com/support/certification</URL>
					<Title>Compatible Application Check</Title>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetApiAccessRules -->
	<xs:element name="GetApiAccessRulesResponse" type="ns:GetApiAccessRulesResponseType"/>
	<xs:complexType name="GetApiAccessRulesResponseType">
		<xs:annotation>
			<xs:documentation>
				Responds to a call to GetApiAccessRules.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ApiAccessRule" type="ns:ApiAccessRuleType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Contains the description of an API access rule, including the
								call name, the application's current daily and hourly usage,
								and other values.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetApiAccessRules</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAttributesCS -->
	<xs:element name="GetAttributesCSRequest" type="ns:GetAttributesCSRequestType"/>
	<xs:complexType name="GetAttributesCSRequestType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!--  &lt;b&gt;No longer recommended.&lt;/b&gt; This is an older format for describing 
				item specifics using an ID-based model.  
				New applications should not use ID-based attributes. 
				Existing applications should be updated to remove all dependencies
				on ID-based attributes now. Instead, use GetCategorySpecifics for the 
				newer Custom Item Specifics model.&lt;br&gt;
				&lt;br&gt;
				Retrieves an XML string that describes how to present Item
				Specifics to a seller who is creating a new listing.
				Use this information to present users with
				the equivalent of the Item Specifics portion of the eBay Title
				and Description pages and to validate selected eBay attributes on
				the client before including them in an AddItem call or related
				calls. The XML string contains a list of all the attributes that
				are applicable for one or more requested categories, along with
				related meta-data. The meta-data specifies all the possible
				values of each attribute, the logic for presenting the attributes
				to a user, and rules for validating the user's selections. &lt;br&gt;
				&lt;br&gt;
				See the eBay Web Services Guide for an overview of Item Specifics and
				details about the eBay attribute model. -->
			</xs:documentation>
			<xs:appinfo>
<!--				<Summary>
					No longer applicable to any category.
				</Summary>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>Avoid</DeprecationDetails>
				<UseInstead>GetCategorySpecifics</UseInstead>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<TempInfo>DetailLevel</TempInfo>
-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AttributeSystemVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A version of the Item Specifics definitions (attribute meta-data)
								for the site.
								Typically, an application passes the version value that was
								returned the last time the application executed this call.
								Filter that causes the call to return only the characteristic sets
								for which the attribute meta-data has changed since the specified
								version. If not specified, all characteristics sets are returned.
								The latest version value is not necessarily greater than the
								previous value that was returned. Therefore, when comparing
								versions, only compare whether the value has changed.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
	<!--							<CallInfo>
									<CallName>GetAttributesCS</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
	-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AttributeSetID" type="xs:int" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								An array of characteristic setIDs (which always correspond to
								attribute set IDs).
								Each characteristic setcorresponds to a level in the eBay
								category hierarchy at
								which all items share common characteristics.
								Multiple categories can be mapped to the same characteristic set.
								AttributeSetIDs is an optional input. When IDs are specified,
								the call only returns meta-data for the corresponding
								characteristic sets.
								When no IDs are specified, the call returns all the current
								attribute meta-data in the system.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
	<!--							<CallInfo>
									<CallName>GetAttributesCS</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
	-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeCategoryMappingDetails" type="xs:boolean" default="false" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								If true, includes a list of CategoryMapping nodes in the response.
								Each CategoryMapping node specifies category information as well as
								attributes and values that your application can auto-fill for
								items listed in that category. See the eBay Web Services Guide for more
								information about options for maintaining category data and
								auto-filling Item Specifics.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
	<!--							<CallInfo>
									<CallName>GetAttributesCS</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
	-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAttributesCS -->
	<xs:element name="GetAttributesCSResponse" type="ns:GetAttributesCSResponseType"/>
	<xs:complexType name="GetAttributesCSResponseType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!--  No longer applicable for any categories.  -->
			</xs:documentation>
			<xs:appinfo>
	<!--
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>Avoid</DeprecationDetails>
				<UseInstead>GetCategorySpecifics</UseInstead>
				<EndOfLifeVersion>889</EndOfLifeVersion>
	-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AttributeSystemVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Current version of the Item Specifics meta-data system for
								the site.
								This value changes each time changes are made to the meta-data.
								The current version value is not necessarily greater than
								the previous value. Therefore, when comparing versions, only
								compare whether the value has changed.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
	<!--							<CallInfo>
									<CallName>GetAttributesCS</CallName>
									<Details>DetailLevel: none</Details>
									<Returned>Always</Returned>
								</CallInfo>
	-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AttributeData" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A string containing a list of all the attributes that are
								applicable to the site (or characteristic sets in the request),
								along with related meta-data.
								The meta-data specifies all the possible values of each attribute,
								the logic for presenting attributes to a user, and rules for
								validating the user's selections. Individual
								elements are not described in the eBay schema format.
								For information about each element in the AttributeData string,
								see the attribute model documentation in the
								eBay Web Services guide (see links below).&lt;br&gt;
								&lt;br&gt;
								Because this is returned as a string, the XML markup elements
								are escaped with character entity references (e.g.,
								&amp;amp;lt;eBay&amp;amp;gt;&amp;amp;lt;Attributes&amp;amp;gt;
								...).
								See the appendices in the eBay Web Services guide for general
								information about string data types.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
	<!--							<CallInfo>
									<CallName>GetAttributesCS</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
	-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAttributesXSL -->
	<xs:element name="GetAttributesXSLRequest" type="ns:GetAttributesXSLRequestType"/>
	<xs:complexType name="GetAttributesXSLRequestType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- &lt;b&gt;No longer recommended.&lt;/b&gt; This supports an older format for describing 
				item specifics using an ID-based model. 
				Most eBay categories no longer support ID-based attributes.
				The remaining categories (e.g., US eBay Motors) will drop support 
				for ID-based attributes by May 2012. 
				New applications should not use ID-based attributes. 
				Existing applications should be updated to remove all dependencies
				on ID-based attributes now. Instead, use GetCategorySpecifics for the 
				newer Custom Item Specifics model.&lt;br&gt;
				&lt;br&gt;
				Retrieves the Item Specifics SYI XSL stylesheet. Apply the stylesheet to the
				XML returned from a call to GetAttributesCS or GetProductSellingPages to
				render a form like the Item Specifics portion of eBay's Title and Description page.
				See the eBay Web Services Guide for an overview of Item Specifics and information
				on working with the XSL.  -->
			</xs:documentation>
			<xs:appinfo>
<!--
				<Summary>
					No longer applicable to any category.
				</Summary>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>Avoid</DeprecationDetails>
				<UseInstead>GetCategorySpecifics</UseInstead>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<TempInfo>DetailLevel</TempInfo>
-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="FileName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								The name of the XSL file to retrieve. If not specified, the call
								returns the latest versions of all available XSL files.
								FileName is an optional input. Valid values&lt;br&gt;
								&lt;br&gt;
                  syi_attributes.xsl
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
			<!--					<CallInfo>
									<CallName>GetAttributesXSL</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
			-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FileVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								The desired version of the XSL file. Required if FileName is specified.
								If not specified, the call returns the latest version of the file.
								(This is not a filter for retrieving changes to the XSL file.)
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
				<!--				<CallInfo>
									<CallName>GetAttributesXSL</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
				-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetAttributesXSL -->
	<xs:element name="GetAttributesXSLResponse" type="ns:GetAttributesXSLResponseType"/>
	<xs:complexType name="GetAttributesXSLResponseType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- No longer applicable to any categories.  -->
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="XSLFile" type="ns:XSLFileType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Child elements contain data related to one XSL file.
 								Multiple XSLFile objects can be returned. However, currently only
 								one is returned.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
		<!--
								<DeprecationVersion>773</DeprecationVersion>
								<DeprecationDetails>Avoid</DeprecationDetails>
								<UseInstead>GetCategorySpecifics</UseInstead>
								<EndOfLifeVersion>889</EndOfLifeVersion>
								<CallInfo>
									<CallName>GetAttributesXSL</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
		-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetBestOffers -->
	<xs:element name="GetBestOffersRequest" type="ns:GetBestOffersRequestType"/>
	<xs:complexType name="GetBestOffersRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves Best Offers.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>RespondToBestOffer, PlaceOffer</RelatedCalls>
				<SeeLink>
					<Title>Enabling Best Offer</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EnablingBestOffer</URL>
				</SeeLink>
				<SeeLink>
					<Title>Email and Address Privacy Policy</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EmailPrivacyPolicy</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the listing for which Best Offer information is to be returned.
								See the description of GetBestOffers
								for details related to who makes the request and how
								ItemID and BestOfferID can be omitted.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetBestOffers</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BestOfferID" type="ns:BestOfferIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the Best Offer for which information is to be returned.
								See the description of GetBestOffers
								for details related to who makes the request and how
								ItemID and BestOfferID can be omitted.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBestOffers</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BestOfferStatus" type="ns:BestOfferStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This optional filter controls whether only active Best Offers are retrieved or
								all Best Offers (even Best Offers that were declined or all no longer the "best
								offer"). The "All" value can only be specified if an &lt;b&gt;ItemID&lt;/b&gt; 
								value is also supplied in the request.
							</xs:documentation>
							<xs:appinfo>
								<Default>Active</Default>
								<CallInfo>
									<CallName>GetBestOffers</CallName>
									<OnlyTheseValues>All, Active</OnlyTheseValues>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies how to create virtual pages in the returned list (such as total
								number of entries and total number of pages to return).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBestOffers</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetBestOffers -->
	<xs:element name="GetBestOffersResponse" type="ns:GetBestOffersResponseType"/>
	<xs:complexType name="GetBestOffersResponseType">
		<xs:annotation>
			<xs:documentation>
				All Best Offers for the item according to the filter or Best Offer
				ID (or both) used in the input.
				For the notification client usage, this response includes a
				single Best Offer.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="BestOfferArray" type="ns:BestOfferArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								All Best Offers for the item according to the filter or
								Best Offer id (or both) used in the input. The buyer and
								seller messages are returned only if the detail level is
								defined. Includes the buyer and seller message only if the
								ReturnAll detail level is used.
								Only returned if Best Offers have been made.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBestOffers</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The item for which Best Offers are being returned.
								Only returned if Best Offers have been made.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBestOffers</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemBestOffersArray" type="ns:ItemBestOffersArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A collection of details about the Best Offers received for a specific item. Empty if there are no Best Offers.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBestOffers</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the number of the page of data to return in the response.
								Default is 1 for most calls. For some calls, the default is 0. Specify a
								positive value equal to or lower than the number of pages available (which you
								determine by examining the results of your initial request).
								See the documentation for other individual calls to determine the correct
								default value. For GetOrders, PageNumber is only applicable to Half.com (is not
								applicable to eBay.com).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<Min>1</Min>
									<Default>1</Default>
									<CallName>GetBestOffers</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides information about the data returned, including the number of pages and the number
								of entries.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBestOffers</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetBidderList -->
	<xs:element name="GetBidderListRequest" type="ns:GetBidderListRequestType"/>
	<xs:complexType name="GetBidderListRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves all items the user is currently bidding on, and the ones they have won
				or purchased.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddItem, GetItem, GetSellerList, RelistItem, ReviseItem</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:annotation>
				<xs:documentation>
					Retrieves all items the user is currently bidding on, and the ones they have won
					or purchased.
				</xs:documentation>
			</xs:annotation>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ActiveItemsOnly" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether or not to limit the result set to active items. If true, only
								active items are returned and the EndTimeFrom and EndTimeTo filters are
								ignored. If false (or not sent), both active and ended items are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBidderList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Used in conjunction with EndTimeTo. Limits returned items to only those for
								which the item's end date is on or after the date-time specified. Specify an
								end date within 30 days prior to today. Items that ended more than 30 days
								ago are omitted from the results. If specified, EndTimeTo must also be
								specified. Express date-time in the format YYYY-MM-DD HH:MM:SS, and in GMT.
								(For information on how to convert between your local time zone and GMT, see
								Time Values Note.) This field is ignored if ActiveItemsOnly is true.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBidderList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Used in conjunction with EndTimeFrom. Limits returned items to only those for
								which the item's end date is on or before the date-time specified. If
								specified, EndTimeFrom must also be specified. Express date-time in the format
								YYYY-MM-DD HH:MM:SS, and in GMT. This field is ignored if ActiveItemsOnly is
								true. Note that for GTC items, whose end times automatically increment by 30
								days every 30 days, an EndTimeTo within in the first 30 days of a listing will
								refer to the listing's initial end time.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBidderList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The user for whom information should be returned. If
								provided, overrides user defined via RequesterCredentials
								in header.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBidderList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="GranularityLevel" type="ns:GranularityLevelCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								You can control some of the fields returned in the response by specifying one
								of two values in the GranularityLevel field: Fine or Medium. Fine returns
								more fields than the default, while setting this field to Medium returns an
								abbreviated set of results.
							</xs:documentation>
							<xs:appinfo>
								<PresentDetails>Yes</PresentDetails>
								<CallInfo>
									<CallName>GetBidderList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetBidderList -->
	<xs:element name="GetBidderListResponse" type="ns:GetBidderListResponseType"/>
	<xs:complexType name="GetBidderListResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to a GetBidderList call, which retrieves all items the user is currently bidding on, or
				has won or purchased.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:annotation>
				<xs:documentation>
					Response to GetBidderListRequest.
				</xs:documentation>
			</xs:annotation>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Bidder" type="ns:UserType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Data for one eBay bidder.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBidderList</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BidItemArray" type="ns:ItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Array of items the bidder has bid on, has won or has lost.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetBidderList</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategories -->
	<xs:element name="GetCategoriesRequest" type="ns:GetCategoriesRequestType"/>
	<xs:complexType name="GetCategoriesRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the latest eBay category hierarchy for a given eBay site.
				Information returned for each category includes the category name
				and the unique ID for the category (unique within the eBay site for which
				categories are retrieved). A category ID is a required input when you list most items.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Retrieves the latest eBay category hierarchy for a given eBay site.
					Information returned for each category includes the category name
					and the unique ID for the category (unique within the eBay site for which
					categories are retrieved). A category ID is a required input when you list most items.
				</Summary>
				<TempInfo>DetailLevel</TempInfo>
				<SeeLink>
					<Title>Categories</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CategoryOverview</URL>
				</SeeLink>
				<RelatedCalls>
					GetCategoryFeatures,
					GetCategoryMappings, GetCategorySpecifics, GetSuggestedCategories
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CategorySiteID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the eBay site for which to retrieve the category
								hierarchy.
								Use the numeric site code (e.g., 77 for eBay Germany).
								Only necessary if you want to retrieve category data
								for a site other than the site from which you are
								submitting the request.
								&lt;br&gt;
								&lt;br&gt;
								NOTE: If you are using the GetCategories call with eBay Motors, you
								must set the Site ID in the Request Header to 0, and then set
								the CategorySiteID to 100. These are both required fields when
								using GetCategories with eBay Motors.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<RequiredInput>No</RequiredInput>
									<Default>The site ID of the request</Default>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryParent" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the ID of the highest-level category to return,
								along with its subcategories.
								If no parent category is specified, all categories are
								returned for the specified site. (Please do not pass a value of 0; zero (0) is an invalid value for CategoryParent.)
								To determine available category IDs, call GetCategories with
								no filters and use a DetailLevel value of ReturnAll.
								If you specify multiple parent categories, the hierarchy for
								each one is returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<RequiredInput>No</RequiredInput>
									<Default />
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LevelLimit" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the maximum depth of the category hierarchy to retrieve,
								where the top-level categories (meta-categories) are at level 1.
								Retrieves all category nodes with a category level less than or
								equal to this value.
								If not specified, retrieves categories at all applicable levels.
								As with all calls, the actual data returned will vary depending
								on how you configure other fields in the request
								(including DetailLevel).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<RequiredInput>No</RequiredInput>
									<Default>0</Default>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ViewAllNodes" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This flag controls whether all eBay categories (that satisfy input filters) are
								returned, or only leaf categories (you can only list items in leaf categories)
								are returned. The default value is 'true', so if this field is omitted, all eBay
								categories will be returned. If you only want to retrieve leaf categories,
								include this flag and set it to 'false'. The actual data returned will vary
								depending on how you configure other fields in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<RequiredInput>No</RequiredInput>
									<Default>true</Default>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategories -->
	<xs:element name="GetCategoriesResponse" type="ns:GetCategoriesResponseType"/>
	<xs:complexType name="GetCategoriesResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the category data for the eBay site specified as input. The category
				data is contained in a CategoryArrayType object, within which are zero, one, or
				multiple CategoryType objects. Each CategoryType object contains the detail data
				for one category. Other fields tell how many categories are returned in a call,
				when the category hierarchy was last updated, and the version of the category
				hierarchy (all three of which can differ from one eBay site to the next).
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CategoryArray" type="ns:CategoryArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								List of the returned categories. The category array contains one CategoryType
								object for each returned category. Returns empty if no detail level is specified.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryCount" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the number of categories returned (i.e., the number of CategoryType
								objects in CategoryArray).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UpdateTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the last date and time that eBay modified the category hierarchy for the
								specified eBay site.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<Details>DetailLevel: ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the version of the category hierarchy on the
								specified eBay site.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<Details>DetailLevel: ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReservePriceAllowed" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							If true, ReservePriceAllowed indicates that all categories on the
							site allow the seller to specify a reserve price for an item.
							If false, this field is not returned in the response and all categories on the site do not normally allow sellers to specify reserve prices.
							The Category.ORPA (override reserve price allowed) field can override (or toggle)
							the reserve price allowed setting for a given category.
							For example, if ReservePriceAllowed is false and Category.ORPA is true,
							the category overrides the site setting and supports reserve prices.
							If ReservePriceAllowed is true and Category.ORPA is true, the category
							overrides the site setting and does does not support reserve prices.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<Details>DetailLevel: ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MinimumReservePrice" type="xs:double" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
	    					Indicates the lowest possible reserve price allowed for any item
	    					listed in any category on the site. You can use the fields returned by GetCategoryFeatures to determine if a different Minimum Reserve Price is defined for the category you want to use.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<Details>DetailLevel: ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReduceReserveAllowed" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							If true, ReduceReserveAllowed indicates that all categories on the
							site allow the seller to reduce an item's reserve price.
							If false, this field is not returned in the response and all categories on the site do not normally allow sellers to reduce an
							item's reserve price.
							The Category.ORRA (override reduce reserve price) field can override (or toggle)
							the reserve price reduction setting for a given category.
							For example, if ReduceReserveAllowed is false and Category.ORRA is true,
							the category overrides the site setting and supports reducing reserve prices.
							If ReduceReserveAllowed is true and Category.ORRA is true, the category
							overrides the site setting and does does not support reducing reserve prices.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategories</CallName>
									<Details>DetailLevel: ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategory2CS -->
	<xs:element name="GetCategory2CSRequest" type="ns:GetCategory2CSRequestType"/>
	<xs:complexType name="GetCategory2CSRequestType">
		<xs:annotation>
			<xs:documentation>
				No longer recommended in general, although this call may still be used to 
				determine whether a category is catalog-enabled. All other features of this call 
				are no longer functional.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					No longer recommended.
				</Summary>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of a category for which to retrieve mappings.
								If not specified, the call
								retrieves a map for all categories.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>GetCategory2CS</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AttributeSystemVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A version of the mappings for the site.
								Typically, an application passes the version value that was returned the last
								time the application executed this call.
								Filter that causes the call to return only the categories
								for which the mappings have changed since the specified version.
								If not specified, all category-to-characteristics set mappings are returned.
								This value changes each time changes are made to the mappings.
								The current version value is not necessarily greater than the previous
								value. Therefore, when comparing versions, only compare whether the
								value has changed.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategory2CS</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategory2CS -->
	<xs:element name="GetCategory2CSResponse" type="ns:GetCategory2CSResponseType"/>
	<xs:complexType name="GetCategory2CSResponseType">
		<xs:annotation>
			<xs:documentation>
				Only applicable for determining whether a category is catalog-enabled.
			</xs:documentation>
			<xs:appinfo>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>Avoid</DeprecationDetails>
				<UseInstead>GetCategoryFeatures, FindProducts</UseInstead>
				<EndOfLifeVersion>889</EndOfLifeVersion>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="MappedCategoryArray" type="ns:CategoryArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains data about categories that are mapped to characteristics sets.
								Use this data to determine:&lt;br&gt;
								- The names and IDs of the characteristics sets&lt;br&gt;
								- The availability of the Pre-filled Item Information feature for listings in that category
									(i.e., whether the category is catalog-enabled)&lt;br&gt;
								- For catalog-enabled categories, the available product search methods&lt;br&gt;
								- The current version information for the complete mapping&lt;br&gt;
								- The version information for each characteristics set
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategory2CS</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UnmappedCategoryArray" type="ns:CategoryArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains data about categories (if any) whose characteristics set mappings have changed
								since the version specified in the request. When a characteristics set mapping
								changes, the data appears in both the UnmappedCategoryArray object
								(to indicate that the change occurred) and the MappedCategoryArray object.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategory2CS</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
									<DeprecationVersion>773</DeprecationVersion>
									<DeprecationDetails>Avoid</DeprecationDetails>
									<UseInstead/>
									<EndOfLifeVersion>889</EndOfLifeVersion>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AttributeSystemVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Current version of the mappings for the site.
								This value changes each time changes are made to the mappings.
								The current version value is not necessarily greater than the previous
								value. Therefore, when comparing versions, only compare whether the
								value has changed.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategory2CS</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SiteWideCharacteristicSets" type="ns:SiteWideCharacteristicsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								A list of one or more characteristics sets mapped to the category, if any. Use this
								information when working with Item Specifics (Attributes) and Pre-filled Item
								Information (Catalogs) functionality.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategory2CS</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
									<DeprecationVersion>773</DeprecationVersion>
									<DeprecationDetails>Avoid</DeprecationDetails>
									<UseInstead>GetCategoryFeatures</UseInstead>
									<EndOfLifeVersion>889</EndOfLifeVersion>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategoryFeatures -->
	<xs:element name="GetCategoryFeaturesRequest" type="ns:GetCategoryFeaturesRequestType"/>
	<xs:complexType name="GetCategoryFeaturesRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns information about the features that are applicable to different categories,
				such as listing durations, shipping term requirements, and Best Offer support.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<SeeLink>
					<Title>Categories</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CategoryOverview</URL>
				</SeeLink>
				<RelatedCalls>GetCategories, GetCategorySpecifics, GeteBayDetails</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the category for which you want to retrieve the feature settings.
								&lt;br&gt;&lt;br&gt;
								Specify a CategoryID, set DetailLevel to ReturnAll, and set
								ViewAllNodes to true to return the default site settings, the
								overrides for the specified category, plus all the child
								categories that have overrides on the features they inherit.
								&lt;br&gt;&lt;br&gt;
								If you also set AllFeaturesForCategory to true, eBay returns the site
								defaults, plus all the settings for the specified category. Child
								category information is not returned in this case.
								&lt;br&gt;&lt;br&gt;
								If CategoryID is not specified, eBay returns the feature settings for
								the site. To return details on all categories that have overrides on
								the properties they inherit, set DetailLevel to ReturnAll, and set
								ViewAllNodes to true. If you also set AllFeaturesForCategory to true,
								eBay returns only the site defaults with no child category information.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LevelLimit" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A level of depth in the category hierarchy. Retrieves all category
								nodes with a CategoryLevel less than or equal to the LevelLimit
								value.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ViewAllNodes" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								You must set DetailLevel to ReturnAll in order to correctly populate the
								response when you set ViewAllNodes to true. In this case, eBay returns the
								site defaults along with all the categories that override the feature
								settings they inherit. Here, each Category container shows only the
								features that it has overridden from its parent node.
								&lt;br&gt;&lt;br&gt;
								If you also specify a CategoryID, eBay returns the details for that category,
								along with containers for each of its child categories that have feature
								overrides.
								&lt;br&gt;&lt;br&gt;
								Note that if ViewAllNodes is set to false (the default) and DetailLevel is
								set to ReturnAll, eBay returns only the leaf categories that have features
								that override the settings they inherit. In this case, the call will not
								return leaf categories that do not have overrides.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<RequiredInput>No</RequiredInput>
									<Default>false</Default>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FeatureID" type="ns:FeatureIDCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Use this field if you want to know if specific features are enabled at the site
								or root category level. Multiple &lt;b&gt;FeatureID&lt;/b&gt; elements can be
								used in the request. If no &lt;b&gt;FeatureID&lt;/b&gt; elements are used, the
								call retrieves data for all features, as applicable to the other request 
								parameters.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<RequiredInput>No</RequiredInput>
									<Default/>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AllFeaturesForCategory" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Use this switch to view all of the feature settings for a specific category.
								All feature settings are returned, regardless of the site default settings.
								This element works in conjunction with CategoryID--refer to the notes for
								that element for more details.
								&lt;br&gt;&lt;br&gt;
								If you also set FeatureID, eBay returns the status of the specified
								features only, for the specified category.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<RequiredInput>No</RequiredInput>
									<Default>false</Default>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategoryFeatures -->
	<xs:element name="GetCategoryFeaturesResponse" type="ns:GetCategoryFeaturesResponseType"/>
	<xs:complexType name="GetCategoryFeaturesResponseType">
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CategoryVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the current version of the set of feature meta-data.
								Compare this value to the version of the last version you
								downloaded to determine whether the data may have changed.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<Details>DetailLevel: none, ReturnSummary, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UpdateTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Gives the time in GMT that the feature flags for the
								category hierarchy were last updated.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<Details>DetailLevel: none, ReturnSummary, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category" type="ns:CategoryFeatureType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								A category whose feature settings are different from the settings of its parent category.&lt;br&gt;
								&lt;br&gt;
								For example, suppose there is a branch of the category tree with 5 category levels
								(L1, L2, L3, L4, and L5). Suppose the feature settings for SiteDefaults, L1, L4, and L5
								are all "A", and the settings for L2 and L3 are "B". In this case:&lt;br&gt;
								L1's settings (A) match the site default, so L1 is not returned.&lt;br&gt;
								L2's settings (B) are different from L1's, so L2 is returned.&lt;br&gt;
								L3's settings (B) are the same as L2's, so L3 is not returned&lt;br&gt;
								L4's settings (A) are different from L3's, so L4 is returned&lt;br&gt;
								L5's settings (A) are the same as L4's, so L5 is not returned.&lt;br&gt;
								&lt;br&gt;
								If you specified a particular FeatureID in the request, this field
								only returns feature settings for that feature.
								Only returned when the category is different from its parent.
								If the category has children and they aren't returned,
								it means the children inherit the category's feature settings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SiteDefaults" type="ns:SiteDefaultsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the feature settings defined for most categories on the site.
								Most categories share these settings. However, some categories can
								override some settings, as indicated in the Category nodes
								(if any).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FeatureDefinitions" type="ns:FeatureDefinitionsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns definitions of the various features on the site,
								or the features you requested in FeatureID (if any).
								Each feature has a node within FeatureDefinitions.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryFeatures</CallName>
									<Details>DetailLevel: none, ReturnSummary, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategoryMappings -->
	<xs:element name="GetCategoryMappingsRequest" type="ns:GetCategoryMappingsRequestType"/>
	<xs:complexType name="GetCategoryMappingsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a map of old category IDs and corresponding active
				category IDs defined for the site to which the request is sent.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					GetCategories, GetCategoryFeatures
				</RelatedCalls>
				<TempInfo>DetailLevel</TempInfo>
				<SeeLink>
					<Title>Maintaining Category Data</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CategoryMapping</URL>
				</SeeLink>
				<SeeLink>
					<Title>Maintaining Category Data</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CategorySync</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CategoryVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								 A version of the category mapping for the site. Filters
								 out data from the call to return only the category
								 mappings for which the data has changed since the
								 specified version. If not specified, all category
								 mappings are returned. Typically, an application passes
								 the version value of the last set of category mappings
								 that the application stored locally. The latest version
								 value is not necessarily greater than the previous value
								 that was returned. Therefore, when comparing versions,
								 only compare whether the value has changed.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryMappings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategoryMappings -->
	<xs:element name="GetCategoryMappingsResponse" type="ns:GetCategoryMappingsResponseType"/>
	<xs:complexType name="GetCategoryMappingsResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns a map of old category IDs and corresponding active category IDs defined
				for the site to which the request was sent. Typically used to update an older item
				definition with a new category ID prior to listing the item.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CategoryMapping" type="ns:CategoryMappingType" minOccurs="0" maxOccurs="unbounded">
					<xs:annotation>
						<xs:documentation>
							Mapping between an old category ID and an active category ID. Returned when
							category mappings exist and the value of CategoryVersion is different from
							the current version on the site.
						</xs:documentation>
						<xs:appinfo>
							<CallInfo>
								<CallName>GetCategoryMappings</CallName>
								<Details>DetailLevel: ReturnAll</Details>
								<Returned>Conditionally</Returned>
							</CallInfo>
						</xs:appinfo>
					</xs:annotation>
					</xs:element>
					<xs:element name="CategoryVersion" type="xs:string" minOccurs="0" maxOccurs="1">
						<xs:annotation>
							<xs:documentation>
								Version value assigned to the current category mapping data for the site.
								Compare this value to the version value the application stored with the mappings
								the last time the application executed the call. If the versions are the same,
								the data has not changed since the last time the data was retrieved and stored.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategoryMappings</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategorySpecifics -->
	<xs:element name="GetCategorySpecificsRequest" type="ns:GetCategorySpecificsRequestType"/>
	<xs:complexType name="GetCategorySpecificsRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns the most popular custom Item Specific names and values for each
				leaf category you request.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddItem, GetCategories, GetCategoryFeatures
				</RelatedCalls>
				<TempInfo>samples</TempInfo>
				<SeeLink>
					<Title>Working with Custom Item Specifics</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ItemSpecifics</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								A leaf-level eBay category ID. This call retrieves recommended
								Item Specifics (if any) for each leaf category you specify.
								(The call returns no results for a parent category.)
								To determine which leaf categories support listing with custom
								Item Specifics, use GetCategoryFeatures.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								This call may return recommendations for categories that don't
								support listing with custom Item Specifics. That is, the
								presence of recommendations for a category does not necessarily
								mean that AddItem supports custom Item Specifics for that
								category and site.
								&lt;/span&gt;
								&lt;br&gt;&lt;br&gt;
								The request requires either CategoryID, CategorySpecfics.CategoryID, or
								CategorySpecificsFileInfo (or the call returns an error). CategoryID and
								CategorySpecific.CategoryID can both be used in the same request.
								(CategorySpecific offers more options to control the response.)
								Some input fields, such as IncludeConfidence, only work when 
								CategoryID or CategorySpecfics.CategoryID is specified.
								&lt;br&gt;&lt;br&gt;
								You can specify multiple leaf categories, but more categories can result in
								longer response times. If your request times out, specify fewer IDs. If you
								specify the same ID twice, we use the first instance.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<MaxOccurs>100</MaxOccurs>
									<CallName>GetCategorySpecifics</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LastUpdateTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Causes the recommendation engine to check whether the list of
								popular Item Specifics for each specified category has changed
								since this date and time. If specified, this call returns no
								Item Specifics; it only returns whether the data has changed
								for any of the requested categories.&lt;br&gt;
								&lt;br&gt;
								Typically, you pass in the Timestamp that was
								returned the last time you refreshed the list of names and values
								for the same categories. If the Updated flag returns true for any
								categories in the response, call GetCategorySpecifics again
								for those categories to get the latest names and values.
								(As downloading all the data may affect your application's
								performance, it may help to only download Item Specifics
								for a category if they have changed since you last checked.)
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MaxNames" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Maximum number of Item Specifics to return
								per category (where each Item Specific is identified
								by a unique name within the category).
								Use this to retrieve fewer results per category.
								For example, if you only want up to 2 per category
								(the top 2 most popular names), specify 2.
							</xs:documentation>
							<xs:appinfo>
								<Min>1</Min>
								<Max>30</Max>
								<Default>10</Default>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MaxValuesPerName" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Maximum number of values to retrieve per item specific. 
								The best practice for using this field depends on your use case.
								For example, if you want all possible values (such as all brands 
								and sizes in a clothing category), then specify a very large 
								number. (This is recommended in most cases.) If you only want the most popular value (like the most popular color), then specify a small number.
							</xs:documentation>
							<xs:appinfo>
								<Min>1</Min>
								<Max>2147483647</Max>
								<Default>25</Default>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Name" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The name of one Item Specific name to find values for.
								Use this if you want to find out whether a name
								that the seller provided has recommended values.
								If you specify multiple leaf categories in the request,
								the recommendation engine returns all matching
								names and values it finds for each of those categories.
								At the time of this writing, this value is case-sensitive.
								(Wildcards are not supported.)&lt;br&gt;
								&lt;br&gt;
								Name and CategorySpecific.ItemSpecific can be used in the
								request. (If you plan to only use one or the other in your application,
								you should use ItemSpecific, as it may offer more options in the future.)
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>30</MaxLength>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategorySpecific" type="ns:CategoryItemSpecificsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Applicable with request version 609 and higher. (This
								does not retrieve data at all if your request version is lower
								than 609.)
								Contains a leaf category for which you want recommended
								Item Specifics, and (optionally) names and values to help
								you refine the recommendations.
								You can specify multiple categories (but more categories
								can result in longer response times). If you specify the same
								category twice, we use the first instance.&lt;br&gt;
								&lt;br&gt;
								Depending on how many recommendations are found, your request
								may time out if you specify too many categories.
								(Typically, you can download recommendations for about 275
								categories at a time.)&lt;br&gt;
								&lt;br&gt;
								CategoryID and CategorySpecific.CategoryID can be used
								in the request. (If you plan to only use one or the other in
								your application, you should use CategorySpecific,
								as it may offer more options in the future.)
							</xs:documentation>
							<xs:appinfo>
								<MaxOccurs>275</MaxOccurs>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExcludeRelationships" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the Relationship node is not returned for any
								recommendations. Relationship recommendations tell you whether
								an Item Specific value has a logical dependency another
								Item Specific.&lt;br&gt;
								&lt;br&gt;
								For example, in a clothing category, Size Type could be
								recommended as a parent of Size, because Size=Small would
								mean something different to buyers depending on whether
								Size Type=Petite or Size Type=Plus.&lt;br&gt;
								&lt;br&gt;
								In general, it is a good idea to retrieve and use relationship
								recommendations, as this data can help buyers find the items
								they want more easily.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<Default>false</Default>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeConfidence" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, returns eBay's level of confidence in the popularity of
								each name and value for the specified category. 
								Some sellers may find this useful when
								choosing whether to use eBay's recommendation or their own
								name or value.&lt;br&gt;
								&lt;br&gt;
								Requires CategoryID to also be passed in.&lt;br&gt;
								&lt;br&gt;
								If you try to use this with CategorySpecificsFileInfo 
								but without	CategoryID, the request fails and no 
								TaskReferenceID or FileReferenceID is returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<Default>false</Default>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategorySpecificsFileInfo" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the response includes FileReferenceID and
								TaskReferenceID. Use these IDs as inputs to the downloadFile
								call in the eBay File Transfer API. That API lets you retrieve
								a single (bulk) GetCategorySpecifics response with all the Item
								Specifics recommendations available for the requested site ID.
								(The downloadFile call downloads a .zip file as an
								attachment.)&lt;br&gt;
								&lt;br&gt;
								Either CategorySpecificsFileInfo or a CategoryID is required
								(or you can specify both). &lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								You can use the File Transfer API without using or learning
								about the Bulk Data Exchange API or other
								Large Merchant Services APIs.
								&lt;/span&gt;
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>downloadFile in the File Transfer API</Title>
									<URL>http://developer.ebay.com/DevZone/file-transfer/CallRef/downloadFile.html</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCategorySpecifics -->
	<xs:element name="GetCategorySpecificsResponse" type="ns:GetCategorySpecificsResponseType"/>
	<xs:complexType name="GetCategorySpecificsResponseType">
		<xs:annotation>
			<xs:documentation>
				Calls made form seller or buyer find out what the most relevant tags and values are for a given category
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Recommendations" type="ns:RecommendationsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
							Contains the most popular Item Specifics, if any, for a category
							specified in the request, or contains information about whether
							the recommendations have changed for that category since
							the LastUpdateTime you requested. &lt;br&gt;
							&lt;br&gt;
							The most relevant Item Specifics (as determined by eBay) 
							are returned first. In many cases, the values are returned in 
							alphabetical order.&lt;br&gt;
							&lt;br&gt;
							This node returns empty (or it's not returned) for a category if
							there is no applicable data (such as when you request a parent category, a category that has no popular Item Specifics yet,
							or a duplicate category that was already returned).
							If you pass in the CategoryID and Name fields together, but no
							matching values are found for the name, eBay returns the name
							with no values (even if the name is not recommended).&lt;br&gt;
							&lt;br&gt;
							If GetCategoryFeatures indicates that custom Item Specifics are
							enabled for a leaf category, but GetCategorySpecifics doesn't
							return any recommendations for that category, the seller can still
							specify their own custom Item Specifics in that category.
							</xs:documentation>
							<xs:appinfo>
								<MaxOccurs>275</MaxOccurs>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TaskReferenceID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Use TaskReferenceID and FileReferenceID as inputs to the
								downloadFile call in the eBay File Transfer API. That API lets
								you retrieve a single (bulk) GetCategorySpecifics response with
								all the Item Specifics recommendations available for the
								requested site ID. (The downloadFile call downloads a .zip file
								as an attachment.)&lt;br&gt;
								&lt;br&gt;
								Only returned when CategorySpecificsFileInfo is passed in the
								request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
								<SeeLink>
									<Title>downloadFile in the File Transfer API</Title>
									<URL>http://developer.ebay.com/DevZone/file-transfer/CallRef/downloadFile.html</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FileReferenceID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Use TaskReferenceID and FileReferenceID as inputs to the
								downloadFile call in the eBay File Transfer API. That API lets
								you retrieve a single (bulk) GetCategorySpecifics response with
								all the Item Specifics recommendations available for the
								requested site ID. (The downloadFile call downloads a .zip file
								as an attachment.)&lt;br&gt;
								&lt;br&gt;
								Only returned when CategorySpecificsFileInfo is passed in the
								request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCategorySpecifics</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
								<SeeLink>
									<Title>downloadFile in the File Transfer API</Title>
									<URL>http://developer.ebay.com/DevZone/file-transfer/CallRef/downloadFile.html</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetChallengeToken -->
	<xs:element name="GetChallengeTokenRequest" type="ns:GetChallengeTokenRequestType"/>
	<xs:complexType name="GetChallengeTokenRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a botblock token and URLs for an image or audio clip that the user is to
				match.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>ValidateChallengeInput, PlaceOffer</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetChallengeToken -->
	<xs:element name="GetChallengeTokenResponse" type="ns:GetChallengeTokenResponseType"/>
	<xs:complexType name="GetChallengeTokenResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to GetChallengeToken request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ChallengeToken" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Botblock token that is used to validate that the user is a human and not a bot.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetChallengeToken</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ImageChallengeURL" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The URL of the image your application should display to
								the user for a botblock challenge.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetChallengeToken</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AudioChallengeURL" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The URL of the audio clip your application should provide for sight-impaired users.
								The audio clip corresponds to the image.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetChallengeToken</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCharities -->
	<xs:element name="GetCharitiesRequest" type="ns:GetCharitiesRequestType"/>
	<xs:complexType name="GetCharitiesRequestType">
		<xs:annotation>
			<xs:documentation>
				Searches for nonprofit charity organizations that meet the
				criteria specified in the request.
				It is recommended that you use at least one input filter, because this call
				no longer returns all charities when made without filters.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Identifying Listings that Benefit Nonprofits</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=IdentifyingListingsThatBenefitNonprofits</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CharityID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identification number assigned by eBay to registered nonprofit
								charity organizations.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCharities</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CharityName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A name assigned to a specified nonprofit
								organization. Accepts full charity nonprofit name
								or partial name as input. For example, enter a
								CharityName of "heart" (case-insensitive) to
								return all charity nonprofits that start with
								"heart." Use with a MatchType value of "Contains"
								to return all charity nonprofits that contain the
								string "heart."
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>150</MaxLength>
								<CallInfo>
									<CallName>GetCharities</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Query" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Accepts a case-insensitive string used to
								find a nonprofit charity organization. Default
								behavior is to search the CharityName field. Use
								with an IncludeDescription value of true to
								include the Mission field in the search.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>350 (characters)</MaxLength>
								<CallInfo>
									<CallName>GetCharities</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CharityRegion" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Region that the nonprofit charity organization is associated
								with. A specific nonprofit charity organization may be associated
								with only one region. Meaning of input values differs depending on
								the site. See GetCharities in the API Developer's Guide for the meaning
								of each input/output value. CharityRegion input value must be
								valid for that SiteID.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCharities</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CharityDomain" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Domain (mission area) that a nonprofit charity organization
								belongs to. Nonprofit charity organizations may belong to multiple
								mission areas. Meaning of input values differs depending on the
								site. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCharities</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeDescription" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Used with Query to search for charity nonprofit
								organizations. A value of true will search the Mission field as
								well as the CharityName field for a string specified in Query.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCharities</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MatchType" type="ns:StringMatchCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the type of string matching to use when a value is submitted in
								CharityName. If no value is specified, default behavior is "StartsWith."
								Does not apply to Query.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCharities</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Featured" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Used to decide if the search is only for featured charities.
								A value of true will search for only featured charities.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCharities</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CampaignID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Reserved for future use.
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCharities -->
	<xs:element name="GetCharitiesResponse" type="ns:GetCharitiesResponseType"/>
	<xs:complexType name="GetCharitiesResponseType">
		<xs:annotation>
			<xs:documentation>
			Contains information about charity nonprofit organizations that meet the
			criteria specified in the request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Charity" type="ns:CharityInfoType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
							Contains information about charity nonprofit organizations that
							meet the criteria specified in the request. One Charity node is
							returned for each applicable nonprofit charity organization. The
							CharityID value is returned as an id attribute of this node. If no
							nonprofit charity organization is applicable, this node is not
							returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
								<CallName>GetCharities</CallName>
								<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetClientAlertsAuthToken -->
	<xs:element name="GetClientAlertsAuthTokenRequest" type="ns:GetClientAlertsAuthTokenRequestType"/>
	<xs:complexType name="GetClientAlertsAuthTokenRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a token required for the GetUserAlerts call in the Client Alerts API.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>SetNotificationPreferences</RelatedCalls>
				<SeeLink>
					<URL>http://developer.ebay.com/DevZone/client-alerts/docs/CallRef/index.html</URL>
					<Title>Client Alerts API Call Reference</Title>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetClientAlertsAuthToken -->
	<xs:element name="GetClientAlertsAuthTokenResponse" type="ns:GetClientAlertsAuthTokenResponseType"/>
	<xs:complexType name="GetClientAlertsAuthTokenResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns a Client Alerts token.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ClientAlertsAuthToken" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This token string is required for the Login call in the Client Alerts API.
								The Client Alerts GetUserAlerts call, which returns alerts about events
								associated with a specific user, requires Login.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetClientAlertsAuthToken</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HardExpirationTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A Client Alerts token expires after seven days.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetClientAlertsAuthToken</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetContextualKeywords -->
	<xs:element name="GetContextualKeywordsRequest" type="ns:GetContextualKeywordsRequestType"/>
	<xs:complexType name="GetContextualKeywordsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves top-ranked contextual eBay keywords and categories
				for a specified web page.
			</xs:documentation>
			<xs:appinfo>
				<ExcludeFromDefaultSites>SG, HK</ExcludeFromDefaultSites>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="URL" type="xs:anyURI" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The URL of the web page from which eBay is to extract keywords.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetContextualKeywords</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Encoding" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Web page encoding by which the URL is to be handled, such as ISO-8859-1.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetContextualKeywords</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The ID of the category to which keywords are to be limited.
								Zero or more category IDs can be specified.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetContextualKeywords</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetContextualKeywords -->
	<xs:element name="GetContextualKeywordsResponse" type="ns:GetContextualKeywordsResponseType"/>
	<xs:complexType name="GetContextualKeywordsResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to a GetContextualKeywords request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ContextSearchAsset" type="ns:ContextSearchAssetType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								An array of either keyword/category pairs or categories, with ranking and score.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetContextualKeywords</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCrossPromotions -->
	<xs:element name="GetCrossPromotionsRequest" type="ns:GetCrossPromotionsRequestType"/>
	<xs:complexType name="GetCrossPromotionsRequestType">
		<xs:annotation>
			<xs:documentation>
				&lt;b&gt;No longer recommended.&lt;/b&gt; The eBay Store Cross Promotions are no longer
				supported in the Trading API. Retrieves a list of upsell or cross-sell items associated
				with the specified Item ID.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetPromotionRules, SetPromotionalSale</RelatedCalls>
				<SeeLink>
					<Title>Cross-Promotions</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CrossPromotionsChapter</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique ID of the referring item. The cross-promoted
								items will supplement this item.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetCrossPromotions</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionMethod" type="ns:PromotionMethodCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The cross-promotion method you want to use for the
								returned list, either UpSell or CrossSell.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCrossPromotions</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionViewMode" type="ns:TradingRoleCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The role of the person requesting to view the cross-promoted
								items, either seller or buyer. Default is buyer.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCrossPromotions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetCrossPromotions -->
	<xs:element name="GetCrossPromotionsResponse" type="ns:GetCrossPromotionsResponseType"/>
	<xs:complexType name="GetCrossPromotionsResponseType">
		<xs:annotation>
			<xs:documentation>
				&lt;b&gt;No longer recommended.&lt;/b&gt; The eBay Store Cross Promotions are no longer supported in the Trading API, so the 
				&lt;b&gt;CrossPromotion&lt;/b&gt; container will either not be returned, or, if it is 
				returned, the data in the container may not be accurate. Returns a list of either upsell or cross-sell items for a given item ID.
				The list can be filtered by the viewer's role, either buyer or seller.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CrossPromotion" type="ns:CrossPromotionsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  eBay Store Cross Promotions are no longer supported in the Trading API, so the
								&lt;b&gt;CrossPromotion&lt;/b&gt; container will either not be returned, or, if it
								is returned, the data in the container may not be accurate. A list of cross-promoted
								items defined for a specific referring item. The list is either upsell or cross-sell
								items, according to the value of &lt;b&gt;PromotionMethod&lt;/b&gt; in 
								&lt;b&gt;GetCrossPromotionsRequest&lt;/b&gt;.
								&lt;br&gt;
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetCrossPromotions</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetDescriptionTemplates -->
	<xs:element name="GetDescriptionTemplatesRequest" type="ns:GetDescriptionTemplatesRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the DescriptionTemplates for a category.
			</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="GetDescriptionTemplatesRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves Theme and Layout specifications for the display of an item's description.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Using Description Templates</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UsingDescriptionTemplatesChapter</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The category for which to retrieve templates. Enter any
								category ID, including Motors vehicle categories. This
								is ignored if you also send MotorVehicles.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LastModifiedTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If specified, only those templates modified on or after the
								specified date are returned. If not specified, all templates are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MotorVehicles" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether to retrieve templates for motor vehicle
								categories for eBay Motors (site 100). If true, templates
								are returned for motor vehicle categories. If false,
								templates are returned for non-motor vehicle categories
								such as Parts and Accessories. If included as an input field (whether true or false), this overrides any value provided for CategoryID.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetDescriptionTemplates -->
	<xs:element name="GetDescriptionTemplatesResponse" type="ns:GetDescriptionTemplatesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns one or more DescriptionTemplate nodes. Each DescriptionTemplate node contains the information for one Theme or one Layout. DescriptionTemplate.DescriptionTemplateType indicates whether it contains data for a Theme or a Layout.
			</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="GetDescriptionTemplatesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returned after calling GetDescriptionTemplatesRequest.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="DescriptionTemplate" type="ns:DescriptionTemplateType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The information for one Theme or one Layout. There
								can be multiple DescriptionTemplates.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LayoutTotal" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The number of Layout templates returned (that is, the
								number of DescriptionTemplates for which Type is "Layout").
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ObsoleteLayoutID" type="xs:int" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The ID of a returned layout that is obsolete. There can be zero or more IDs.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ObsoleteThemeID" type="xs:int" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The ID of a returned theme that is obsolete. There can be zero or more IDs.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ThemeGroup" type="ns:ThemeGroupType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Data for one theme group. There can be multiple
								ThemeGroups in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ThemeTotal" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The number of Theme templates returned (that is, the number
								of DescriptionTemplates for which Type is "Theme").
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDescriptionTemplates</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetDispute -->
	<xs:element name="GetDisputeRequest" type="ns:GetDisputeRequestType"/>
	<xs:complexType name="GetDisputeRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the details of a specific eBay dispute corresponding to the supplied dispute ID.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddDispute, AddDisputeResponse, GetItemTransactions, GetSellerTransactions,
					GetUserDisputes, SellerReverseDispute
				</RelatedCalls>
				<SeeLink>
					<Title>Unpaid Item Disputes</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UnpaidItemDisputes</URL>
				</SeeLink>
				<SeeLink>
					<Title>Buyer Disputes</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BuyerDisputes</URL>
				</SeeLink>
				<SeeLink>
					<Title>Getting Details About a Dispute</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingDetailsAboutADispute</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="DisputeID" type="ns:DisputeIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of an eBay dispute. The caller passes in this value to
								retrieve detailed information on a specific dispute.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDispute</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetDispute -->
	<xs:element name="GetDisputeResponse" type="ns:GetDisputeResponseType"/>
	<xs:complexType name="GetDisputeResponseType">
		<xs:annotation>
			<xs:documentation>
        Returned after calling GetDisputeRequest. Returns the record of
      	a dispute, including the dispute state and other information.
      	&lt;br&gt;&lt;br&gt;Both Sellers and Buyers can use the SellerClosedDispute in
      	Platform Notifications to receive a notification when a dispute has been closed.
      	The notification includes the same data that is returned in the GetDispute response.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Dispute" type="ns:DisputeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The dispute record, containing information about
								the buyer, seller, dispute state, dispute status,
								comments added to the dispute, or resolutions.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetDispute</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetFeedback -->
	<xs:element name="GetFeedbackRequest" type="ns:GetFeedbackRequestType"/>
	<xs:complexType name="GetFeedbackRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the accumulated feedback left for a specified user or the summary
				feedback data for a specific order line item or item listing.&amp;nbsp;&lt;b&gt;Also for
				Half.com&lt;/b&gt;.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>LeaveFeedback, GetSellerDashboard, GetSellerTransactions</RelatedCalls>
				<SeeLink>
					<Title>Leaving and Retrieving Feedback</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Feedback</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Feedback</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeedbackIntro</URL>
				</SeeLink>
				<SeeLink>
					<Title>Getting Feedback Left By Another User</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeedbackGet</URL>
				</SeeLink>
				<SeeLink>
					<Title>Detailed Seller Ratings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=DetailedSellerRatings</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="UserID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the user whose feedback data is to be returned. If not
								specified, then the feedback returned is for the requesting user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FeedbackID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An ID that uniquely identifies a feedback record to be retrieved.
								Used only by the Feedback notification.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. A listing can have multiple
								order line items (transactions), but only one &lt;b&gt;ItemID&lt;/b&gt;. If &lt;b&gt;ItemID&lt;/b&gt; is
								specified in the &lt;b&gt;GetFeedback&lt;/b&gt; request, the returned feedback records are
								restricted to the specified &lt;b&gt;ItemID&lt;/b&gt;. The &lt;b&gt;FeedbackType&lt;/b&gt; and &lt;b&gt;Pagination&lt;/b&gt;
								fields (if included) are ignored. The maximum number of feedback records
								returned is 100.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay order line item (transaction). A
								&lt;b&gt;TransactionID&lt;/b&gt; can be paired up with its corresponding &lt;b&gt;ItemID&lt;/b&gt; and used as
								an input filter in the &lt;b&gt;GetFeedback&lt;/b&gt; request. If an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt;
								pair or an &lt;b&gt;OrderLineItemID&lt;/b&gt; value is used to retrieve a feedback record
								on a specific order line item, the &lt;b&gt;FeedbackType&lt;/b&gt; and &lt;b&gt;Pagination&lt;/b&gt;
								fields (if included) are ignored.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					 <xs:element name="CommentType" type="ns:CommentTypeCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Returns feedback of a specified type (positive, negative, or neutral) in 
								&lt;b&gt;FeedbackDetailArray&lt;/b&gt;. You can include two comment types in your call if you want
								to exclude the third type from your results. If no &lt;b&gt;CommentType&lt;/b&gt; is specified,
								all of the feedback types are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					 <xs:element name="FeedbackType" type="ns:FeedbackTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns feedback that you received as a buyer or seller, or feedback you left
								for others (as either a buyer or a seller). You can include only one
								&lt;b&gt;FeedbackType&lt;/b&gt; in your call. If no &lt;b&gt;FeedbackType&lt;/b&gt; is specified, all of the
								available feedback is returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Controls the pagination of the result set. Child elements, &lt;b&gt;EntriesPerPage&lt;/b&gt; and
								&lt;b&gt;PageNumber&lt;/b&gt;, specify the maximum number of individual feedback records to return
								per call and which page of data to return. Only applicable if &lt;b&gt;DetailLevel&lt;/b&gt; is
								set to &lt;b&gt;ReturnAll&lt;/b&gt; and the call is returning feedback for a &lt;b&gt;UserID&lt;/b&gt;. Feedback
								summary data is not paginated, but when pagination is used, it is returned
								after the last feedback detail entry.
								&lt;br&gt;&lt;br&gt;
								Accepted values for &lt;b&gt;Pagination.EntriesPerPage&lt;/b&gt; for GetFeedback is 25 (the
								default), 50, 100, and 200. If you specify a value of zero, or a value
								greater than 200, the call fails with an error. If you specify a value between
								one and twenty-four, the value is rounded up to 25. Values between 26 and 199
								that are not one of the accepted values are rounded down to the nearest
								accepted value.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>								
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier for an eBay order line item and
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. An &lt;b&gt;OrderLineItemID&lt;/b&gt; can be used as an
								input filter in the &lt;b&gt;GetFeedback&lt;/b&gt; request. If an &lt;b&gt;OrderLineItemID&lt;/b&gt; value is
								used to retrieve a feedback record on a specific order line item, the
								&lt;b&gt;FeedbackType&lt;/b&gt; and &lt;b&gt;Pagination&lt;/b&gt; fields (if included) are ignored.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>100</MaxLength>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					 </xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetFeedback -->
	<xs:element name="GetFeedbackResponse" type="ns:GetFeedbackResponseType"/>
	<xs:complexType name="GetFeedbackResponseType">
		<xs:annotation>
			<xs:documentation>
				The GetFeedback response contains the feedback summary if a 
				TransactionID or ItemID is specified, and contains the specified user's total
				feedback score and feedback summary data if a UserID is specified. If no
				value is supplied, the feedback score and feedback summary for the requesting
				user will be returned. 
				&lt;br&gt;
				If a detail level value of ReturnAll is specified, an array of all feedback 
				records will be returned.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="FeedbackDetailArray" type="ns:FeedbackDetailArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the individual feedback records for the user or order line item specified in the request. There is one FeedbackDetailType
								object for each feedback record. Only populated with data when a detail level of ReturnAll is specified in the request. Not returned if you specify FeedbackID in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FeedbackDetailItemTotal" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the number of FeedbackDetailType objects returned in the
								FeedbackDetailArray property. Only applicable if feedback details are
								returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FeedbackSummary" type="ns:FeedbackSummaryType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Summary feedback data for the user. Contains counts of positive, neutral,
								and negative feedback for pre-defined time periods. Only applicable if feedback details are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FeedbackScore" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the total feedback score for the user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains information regarding the pagination of data (if pagination is
								used), including total number of pages and total number of entries. This
								is only applicable when a User ID or no ID (requester option) is specified.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>					
					<xs:element name="EntriesPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the number of entries (feedback detail) that are being 
								returned per page of data (i.e., per call).  
								Only returned if entries are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates which page of data was just returned. Will be the same as the
								value specified in Pagination.PageNumber. (If the input is
								higher than the total number of pages, the call fails with an error.)
								Only returned if items are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetFeedback</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItem -->
	<xs:element name="GetItemRequest" type="ns:GetItemRequestType"/>
	<xs:complexType name="GetItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns item data such as title, description, price information, seller information, and so on, for the specified &lt;b&gt;ItemID&lt;/b&gt;. &amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<AddToDefaultAreas>half</AddToDefaultAreas>
				<RelatedCalls>
					AddItem, AddFixedPriceItem, GetItems, GetSellerEvents, GetSellerList,
					RelistItem, ReviseItem
				</RelatedCalls>
				<SeeLink>
					<Title>Retrieving Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=RetrievingItems</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the &lt;b&gt;ItemID&lt;/b&gt; that uniquely identifies the item listing for which
								to retrieve the data.
								&lt;br&gt;&lt;br&gt;
								&lt;b&gt;ItemID&lt;/b&gt; is a required input in most cases. &lt;b&gt;SKU&lt;/b&gt; can be used instead in certain
								cases (see the description of SKU). If both &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;SKU&lt;/b&gt; are specified for
								items where the inventory tracking method is &lt;b&gt;ItemID&lt;/b&gt;, &lt;b&gt;ItemID&lt;/b&gt; takes precedence.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeWatchCount" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates if the caller wants to include watch count for that item in the
								response. You must be the seller of the item to retrieve the watch count.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeCrossPromotion" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This flag should no longer be used as eBay Store Cross Promotions are no
								longer supported by the Trading API.
								&lt;br&gt;&lt;br&gt;
								Specifies whether or not to include cross-promotion information for
								the item in the call response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeItemSpecifics" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the response returns the &lt;b&gt;ItemSpecifics&lt;/b&gt; node
								(if the listing has custom Item Specifics).&lt;br&gt;
								&lt;br&gt;
								Item Specifics are well-known aspects of items in a given
								category. For example, items in a washer and dryer category
								might have an aspect like Type=Top-Loading; whereas
								items in a jewelry category might have an aspect like
								Gemstone=Amber.&lt;br&gt;
								&lt;br&gt;
								(This does not cause the response to include ID-based
								attributes. To also retrieve ID-based attributes,
								pass &lt;b&gt;DetailLevel&lt;/b&gt; in the request with the value
								&lt;b&gt;ItemReturnAttributes&lt;/b&gt; or &lt;b&gt;ReturnAll&lt;/b&gt;.)
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>No</RequiredInput>
									<SeeLink>
										<Title>Working with Custom Item Specifics</Title>
										<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ItemSpecifics</URL>
									</SeeLink>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeTaxTable" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, an associated tax table is returned in the response.
								If no tax table is associated with the item, then no
								tax table is returned, even if &lt;b&gt;IncludeTaxTable&lt;/b&gt; is set to true.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Retrieves an item that was listed by the user identified
							in AuthToken and that is being tracked by this SKU.&lt;br&gt;
							&lt;br&gt;
							A SKU (stock keeping unit) is an identifier defined by a seller.
							Some sellers use SKUs to track complex flows of products
							and information on the client side.
							eBay preserves the SKU on the item, enabling you
							to obtain it before and after an order line item is created.
							(SKU is recommended as an alternative to
							ApplicationData.)&lt;br&gt;
							&lt;br&gt;
							In &lt;b&gt;GetItem&lt;/b&gt;, &lt;b&gt;SKU&lt;/b&gt; can only be used to retrieve one of your
							own items, where you listed the item by using &lt;b&gt;AddFixedPriceItem&lt;/b&gt;
							or &lt;b&gt;RelistFixedPriceItem&lt;/b&gt;,
							and you set &lt;b&gt;Item.InventoryTrackingMethod&lt;/b&gt; to &lt;b&gt;SKU&lt;/b&gt; at
							the time the item was listed. (These criteria are necessary to
							uniquely identify the listing by a SKU.)&lt;br&gt;
							&lt;br&gt;
							Either &lt;b&gt;ItemID&lt;/b&gt; or &lt;b&gt;SKU&lt;/b&gt; is required in the request.
							If both are passed, they must refer to the same item,
							and that item must have &lt;b&gt;InventoryTrackingMethod&lt;/b&gt; set to &lt;b&gt;SKU&lt;/b&gt;.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50</MaxLength>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VariationSKU" type="ns:SKUType" minOccurs="0">
					<xs:annotation>
							<xs:documentation>
								Variation-level SKU that uniquely identifes a Variation within
								the listing identified by &lt;b&gt;ItemID&lt;/b&gt;. Only applicable when the
								seller listed the item with Variation-level SKU (&lt;b&gt;Variation.SKU&lt;/b&gt;)
								values. Retrieves all the usual &lt;b&gt;Item&lt;/b&gt; fields, but limits the
								&lt;b&gt;Variations&lt;/b&gt; content to the specified Variation.
								If not specified, the response includes all Variations.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VariationSpecifics" type="ns:NameValueListArrayType" minOccurs="0">
					<xs:annotation>
							<xs:documentation>
								Name-value pairs that identify one or more Variations within the
								listing identified by &lt;b&gt;ItemID&lt;/b&gt;. Only applicable when the seller
								listed the item with Variations. Retrieves all the usual &lt;b&gt;Item&lt;/b&gt;
								fields, but limits the Variations content to the specified
								Variation(s). If the specified pairs do not match any Variation,
								eBay returns all Variations.&lt;br&gt;
								&lt;br&gt;
								To retrieve only one variation, specify the full set of
								name/value pairs that match all the name-value pairs of one
								Variation. &lt;br&gt;
								&lt;br&gt;
								To retrieve multiple variations (using a wildcard),
								specify one or more name/value pairs that partially match the
								desired variations. For example, if the listing contains
								Variations for shirts in different colors and sizes, specify
								Color as Red (and no other name/value pairs) to retrieve
								all the red shirts in all sizes (but no other colors).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for an order line item (transaction). An order line item is created
								when a buyer commits to purchasing an item.
								&lt;br&gt;&lt;br&gt;
								Since you can change active multiple-quantity fixed-price listings even
								after one of the items has been purchased, the &lt;b&gt;TransactionID&lt;/b&gt; is
								associated with a snapshot of the item data at the time of the purchase.
								&lt;br&gt;&lt;br&gt;
								After one item in a multi-quantity listing has been sold, sellers can not
								change the values in the Title, Primary Category, Secondary Category,
								Listing Duration, and Listing Type fields. However, all other fields are
								editable.
								&lt;br&gt;&lt;br&gt;
								Specifying a &lt;b&gt;TransactionID&lt;/b&gt; in the &lt;b&gt;GetItem&lt;/b&gt; request allows you to retrieve
								a snapshot of the listing as it was when the order line item was created.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeItemCompatibilityList" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field is used to specify whether or not to retrieve Parts
								Compatiblity information. If true, any compatible applications associated
								with the item will be returned in the response (&lt;b class="con"&gt;
								Item.ItemCompatibilityList&lt;/b&gt;). If no compatible applications have
								been specified for the item, no item compatibilities will be returned.
								&lt;br&gt;&lt;br&gt;
								If false or not specified, the response will return a compatibility count
								(&lt;b class="con"&gt;ItemCompatibilityCoun&lt;/b&gt;t) when parts
								compatibilities have been specified for the item.
								&lt;br&gt;&lt;br&gt;
								Parts Compatibility is supported in limited Parts &amp; Accessories
								categories for the eBay US Motors (site ID 100) and eBay Germany (site ID
								77) sites only.
							</xs:documentation>
							<xs:appinfo>
								<noCalls/>
								<!-- <Default>false</Default>
								 <CallInfo>
									<CallName>GetItem</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>ItemCompatibilityCount</Title>
									<URL>#Response.Item.ItemCompatibilityCount</URL>
								</SeeLink>
								<SeeLink>
									<Title>ItemCompatibilityList</Title>
									<URL>#Response.Item.ItemCompatibilityList</URL>
								</SeeLink>
								<SeeLink>
									<Title>Listing Items with Parts Compatibility</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=PartsCompatibility</URL>
								</SeeLink>
								-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItem -->
	<xs:element name="GetItemResponse" type="ns:GetItemResponseType"/>
	<xs:complexType name="GetItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the item data returned by the call. The data for the specified item
				listing is returned in an ItemType object.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ItemType object that contains the data for the specified item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItem</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ItemReturnAttributes, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItemRecommendations -->
	<xs:element name="GetItemRecommendationsRequest" type="ns:GetItemRecommendationsRequestType"/>
	<xs:complexType name="GetItemRecommendationsRequestType">
		<xs:annotation>
			<xs:documentation>
				No longer recommended.
			</xs:documentation>
			<xs:appinfo>
				<deprecationVersion>805</deprecationVersion>
				<deprecationDetails>Avoid</deprecationDetails>
				<useInstead/>
				<endOfLifeVersion>915</endOfLifeVersion>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="GetRecommendationsRequestContainer" type="ns:GetRecommendationsRequestContainerType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the data for a single item and configures the recommendation engines to use
								when processing the item.
								To retrieve recommendations for multiple items, pass a separate
								GetRecommendationsRequestContainer for each item. In this case,
								pass a user-defined correlation ID for each item to identify the matching response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemRecommendations</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItemRecommendations -->
	<xs:element name="GetItemRecommendationsResponse" type="ns:GetItemRecommendationsResponseType"/>
	<xs:complexType name="GetItemRecommendationsResponseType">
		<xs:annotation>
			<xs:documentation>
				GetItemRecommendations returns recommended changes or opportunities for improvement
				related to listing data that was passed in the request.
				This call supports batch requests. That is, it can retrieve recommendations for multiple
				items at once.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="GetRecommendationsResponseContainer" type="ns:GetRecommendationsResponseContainerType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies recommended changes or opportunities for improving the data of a single item.
								If multiple items were processed, a separate GetRecommendationsResponseContainer
								is returned for each item. Each container includes a user-defined correlation ID
								to help you match items in the request to recommendations in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemRecommendations</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItemShipping -->
	<xs:element name="GetItemShippingRequest" type="ns:GetItemShippingRequestType"/>
	<xs:complexType name="GetItemShippingRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns shipping cost estimates for an item for every calculated shipping service
				that the seller has offered with the listing. This is analogous to the Shipping
				Calculator seen in both the buyer and seller web pages.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Determining Shipping Costs for a Listing</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ShippingGettingCosts</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The item ID that uniquely identifies the item listing for which
								to retrieve the data. Required input.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetItemShipping</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="QuantitySold" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Number of items sold to a single buyer and to be shipped together.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemShipping</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DestinationPostalCode" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Destination country postal code (or zipcode, for US). Ignored if no
								country code is provided. Optional tag for some countries. More likely to
								be required for large countries.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemShipping</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DestinationCountryCode" type="ns:CountryCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Destination country code. If DestinationCountryCode is US,
								a postal code is required and it represents the US zip code.
							</xs:documentation>
							<xs:appinfo>
								<Default>US</Default>
								<CallInfo>
									<CallName>GetItemShipping</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItemShipping -->
	<xs:element name="GetItemShippingResponse" type="ns:GetItemShippingResponseType"/>
	<xs:complexType name="GetItemShippingResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the data returned by the call. The shipping details for the specified
				item are returned in a ShippingDetails object.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ShippingDetails" type="ns:ShippingDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Shipping-related details for the specified item. Any error about shipping services
								(returned by a vendor of eBay's who calculates shipping costs) is returned in
								ShippingRateErrorMessage. Errors from a shipping service are likely to be related to
								issues with shipping specifications, such as package size and the selected shipping
								method not supported by a particular shipping service.
								&lt;br&gt;
								&lt;br&gt;
								If a buyer buys multiple quantities of an item and the resultant total
								weight exceeds the weight limit of the shipping service, GetItemShipping
								returns the shipping cost and shipping service and internally groups the
								items in separate packages. A shipping service is removed from
								ShippingDetails only if the weight of a single item exceeds the weight
								limit of the shipping service.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemShipping</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItemTransactions -->
	<xs:element name="GetItemTransactionsRequest" type="ns:GetItemTransactionsRequestType"/>
	<xs:complexType name="GetItemTransactionsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves order line item (transaction) information for a specified &lt;b&gt;ItemID&lt;/b&gt;. &amp;
				nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;. The call returns zero, one, or
				multiple order line items, depending on the number of items sold from the listing.
				&lt;br&gt;&lt;br&gt;
				You can retrieve order line item data for a specific time range or
				number of days. If you don't specify a range or number of days, order line item
				data will be returned for the past 30 days.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>GetSellerTransactions, GetOrders, GetOrderTransactions</RelatedCalls>
				<SeeLink>
					<Title>Email and Address Privacy Policy</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EmailPrivacyPolicy</URL>
					<For>the conditions under which buyer and seller email and address are returned.</For>
				</SeeLink>
				<SeeLink>
					<Title>Retrieving Order Line Item Data and Managing Orders</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=RetrievingTransactionsForSingleItem</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. A listing can have multiple
								order line items (transactions), but only one &lt;b&gt;ItemID&lt;/b&gt;. When you use
								&lt;b&gt;ItemID&lt;/b&gt; alone, eBay returns all order line items that are associated with
								the &lt;b&gt;ItemID&lt;/b&gt; (listing). If you pair &lt;b&gt;ItemID&lt;/b&gt; with a specific &lt;b&gt;TransactionID&lt;/b&gt;,
								data on a specific order line item is returned. If &lt;b&gt;OrderLineItemID&lt;/b&gt; is
								specified in the request, any &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair specified in the
								same request will be ignored.
								&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								&lt;b&gt;GetItemTransactions&lt;/b&gt; doesn't support SKU as an input because this
								call requires an identifier that is unique across your active
								and ended listings. Even when &lt;b&gt;InventoryTrackingMethod&lt;/b&gt; is set to
								&lt;b&gt;SKU&lt;/b&gt; in a listing, the SKU is only unique across your active
								listings (not your ended listings). To retrieve order line items
								by SKU, use &lt;b&gt;GetSellerTransactions&lt;/b&gt; or &lt;b&gt;GetOrderTransactions&lt;/b&gt; instead.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The &lt;b&gt;ModTimeFrom&lt;/b&gt; and &lt;b&gt;ModTimeTo&lt;/b&gt; fields specify a date range for retrieving
								order line items associated with the specified &lt;b&gt;ItemID&lt;/b&gt;. The &lt;b&gt;ModTimeFrom&lt;/b&gt;
								field is the starting date range. All eBay order line items that were
								last modified within this date range are returned in the output. The
								maximum date range that may be specified is 30 days. This field is not
								applicable if a specific &lt;b&gt;TransactionID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; is included in
								the request or if the &lt;b&gt;NumberOfDays&lt;/b&gt; date filter is used.
								&lt;br&gt;&lt;br&gt;
								If you don't specify a &lt;b&gt;ModTimeFrom&lt;/b&gt;/&lt;b&gt;ModTimeTo&lt;/b&gt; filter, the &lt;b&gt;NumberOfDays&lt;/b&gt;
								time filter is used and it defaults to 30 (days). 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The &lt;b&gt;ModTimeFrom&lt;/b&gt; and &lt;b&gt;ModTimeTo&lt;/b&gt; fields specify a date range for retrieving
								order line items associated with the specified &lt;b&gt;ItemID&lt;/b&gt;. The &lt;b&gt;ModTimeTo&lt;/b&gt;
								field is the ending date range. All eBay order line items that were last
								modified within this date range are returned in the output. The maximum
								date range that may be specified is 30 days. If the &lt;b&gt;ModTimeFrom&lt;/b&gt; field is
								used and the &lt;b&gt;ModTimeTo&lt;/b&gt; field is omitted, the &lt;b&gt;ModTimeTo&lt;/b&gt; value defaults to
								the present time or to 30 days past the &lt;b&gt;ModTimeFrom&lt;/b&gt; value (if
								&lt;b&gt;ModTimeFrom&lt;/b&gt; value is more than 30 days in the past). This field is not
								applicable if a specific &lt;b&gt;TransactionID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; is included in
								the request or if the &lt;b&gt;NumberOfDays&lt;/b&gt; date filter is used.
								&lt;br&gt;&lt;br&gt;
								If you don't specify a &lt;b&gt;ModTimeFrom&lt;/b&gt;/&lt;b&gt;ModTimeTo&lt;/b&gt; filter, the &lt;b&gt;NumberOfDays&lt;/b&gt;
								time filter is used and it defaults to 30 (days).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Include a &lt;b&gt;TransactionID&lt;/b&gt; field in the request if you want to retrieve the
								data for a specific order line item (transaction). If a &lt;b&gt;TransactionID&lt;/b&gt; is
								provided, any specified time filter is ignored. 
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements control pagination of the output. Use the &lt;b&gt;EntriesPerPage&lt;/b&gt;
								property to control the number of order line items to
								return per call and the &lt;b&gt;PageNumber&lt;/b&gt; property to specify the specific page
								of data to return. If multiple pages of order line items are returned
								based on input criteria and Pagination properties, &lt;b&gt;GetItemTransactions&lt;/b&gt;
								will need to be called multiple times (with the &lt;b&gt;PageNumber&lt;/b&gt; value being
								increased by 1 each time) to scroll through all results.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeFinalValueFee" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether to include the Final Value Fee (FVF) for all order
								line items in the response. The Final Value Fee is
								returned in the &lt;b&gt;Transaction.FinalValueFee&lt;/b&gt; field. The Final Value Fee is
								assessed right after the creation of an order line item.
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeContainingOrder" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Include this field and set it to True if you want the &lt;b&gt;ContainingOrder&lt;/b&gt;
								container to be returned in the response under each &lt;b&gt;Transaction&lt;/b&gt; node.
								For single line item orders, the &lt;b&gt;ContainingOrder.OrderID&lt;/b&gt; value takes the
								value of the &lt;b&gt;OrderLineItemID&lt;/b&gt; value for the order line item. For Combined
								Payment orders, the &lt;b&gt;ContainingOrder.OrderID&lt;/b&gt; value will be shared by at
								least two order line items (transactions) that are part of the same order.
							</xs:documentation>
							<xs:appinfo>
							  <default>false</default>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Platform" type="ns:TransactionPlatformCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Name of the eBay co-branded site upon which the order line item
								was created. This filter can be used to limit the number
								of results that are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NumberOfDays" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This time filter specifies the number of days (24-hour periods) in the
								past to search for order line items. All eBay order line items that were
								either created or modified within this period are returned in the
								response. If specified, &lt;b&gt;NumberOfDays&lt;/b&gt; will override any date range
								specified with the &lt;b&gt;ModTimeFrom&lt;/b&gt;/&lt;b&gt;ModTimeTo&lt;/b&gt; time filters. This field is not
								applicable if a specific &lt;b&gt;TransactionID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; is included in
								the request.
							</xs:documentation>
							<xs:appinfo>
								<default>30</default>
								<Min>1</Min>
								<Max>30</Max>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeVariations" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included in the request and set to True, all variations defined for
								the item are returned at the root level, including variations
								that have no sales. If not included in the request or set to false, the
								variations with sales are still returned in separate &lt;b&gt;Transaction&lt;/b&gt; nodes. This information is intended to help sellers to reconcile their
								local inventory with eBay's records, while processing order line items
								(without requiring a separate call to &lt;b&gt;GetItem&lt;/b&gt;).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Default>false</Default>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for an eBay order line item. This field is created
								as soon as there is a commitment to buy from the seller, and its value
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. If you want to retrieve data on a
								specific order line item, you can use an &lt;b&gt;OrderLineItemID&lt;/b&gt; value in the
								request instead of the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair. If an &lt;b&gt;OrderLineItemID&lt;/b&gt; is
								provided, any specified time filter is ignored. 
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>100</MaxLength>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItemTransactions -->
	<xs:element name="GetItemTransactionsResponse" type="ns:GetItemTransactionsResponseType"/>
	<xs:complexType name="GetItemTransactionsResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns an array of order line item (transaction) data for the item specified in the request.
				The results can be used to create a report of data that is commonly
				necessary for order processing.
				Zero, one, or many &lt;b&gt;Transaction&lt;/b&gt; objects can be returned in the &lt;b&gt;TransactionArray&lt;/b&gt;.
				The set of order line items returned is limited to those that were modified between
				the times specified in the request's &lt;b&gt;ModTimeFrom&lt;/b&gt; and &lt;b&gt;ModTime&lt;/b&gt; filters.
				Also returns the &lt;b&gt;Item&lt;/b&gt; object that spawned the order line items.
				If pagination filters were specified in the request, returns meta-data describing
				the effects of those filters on the current response and the estimated effects if
				the same filters are used in subsequent calls.
				&lt;br&gt;&lt;br&gt;
				Data from the &lt;b&gt;TransactionArray&lt;/b&gt; may be used to trigger the following Platform
				Notifications: EndOfAuction, AuctionCheckoutComplete, FixedPriceEndOfTransaction,
				CheckoutBuyerRequestTotal, FixedPriceTransaction, Checkout,
				FixedPriceTransactionForSeller, FixedPriceTransactionForBuyer, ItemMarkedAsShipped,
				and ItemMarkedAsPaid. Each notification will be based on the state of the item
				(a 'snapshot' of the item) at the time the order line item was created.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the total number of pages (&lt;b&gt;TotalNumberOfPages&lt;/b&gt;) and the total number
								of entries (&lt;b&gt;TotalNumberOfEntries&lt;/b&gt;) that could be returned given repeated calls
								that use the same selection criteria as the call that returned this response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMoreTransactions" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether there are additional order line items (transactions) to retrieve.
								That is, indicates whether more pages of data are available to be
								returned, given the filters that were specified in the request.
								Returns false for the last page of data.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionsPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Number of order line items (transactions) returned per page (per call). May be a higher value
								than &lt;b&gt;ReturnedTransactionCountActual&lt;/b&gt; if the page returned is the last page
								and more than one page of data exists.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Page number for the page of order line items the response returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReturnedTransactionCountActual" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Number of order line items retrieved in the current page of results just returned.
								May be a lower value than &lt;b&gt;TransactionsPerPage&lt;/b&gt; if the page returned is the last
								page and more than one page of data exists.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;Item&lt;/b&gt; object that spawned the order line item. It is a purchase from this item's listing
								that the order line item represents.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionArray" type="ns:TransactionArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								List of &lt;b&gt;Transaction&lt;/b&gt; objects representing the order line items resulting
								from the listing. Each &lt;b&gt;Transaction&lt;/b&gt; object contains the data for one purchase
								(of one or more items in the same listing). The &lt;b&gt;Transaction.Item&lt;/b&gt; field is not
								returned because the &lt;b&gt;Item&lt;/b&gt; object is returned at the root level of the response.
								See the reference guide for more information about the fields that are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PayPalPreferred" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether the item's seller has the preference enabled that shows
								that the seller prefers PayPal as the method of payment for an item. This
								preference is indicated on an item's View Item page and is intended to
								influence a buyer to use PayPal
								to pay for the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItemsAwaitingFeedback -->
	<xs:element name="GetItemsAwaitingFeedbackRequest" type="ns:GetItemsAwaitingFeedbackRequestType"/>
	<xs:complexType name="GetItemsAwaitingFeedbackRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns orders in which the user was involved and for which feedback
				is still needed from either the buyer or seller.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					GetMyeBayBuying, GetMyeBaySelling, GetMyeBayReminders
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="AbstractRequestType">
				<xs:sequence>
					<xs:element name="Sort" type="ns:ItemSortTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies how the returned feedback items should be sorted.
								Valid values are Title, EndTime, QuestionCount, FeedbackLeft,
								FeedbackReceivedDescending, UserIDDescending, TitleDescending,
								and EndTimeDescending.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemsAwaitingFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the number of entries per page and the page number to return
								in the result set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemsAwaitingFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetItemsAwaitingFeedback -->
	<xs:element name="GetItemsAwaitingFeedbackResponse" type="ns:GetItemsAwaitingFeedbackResponseType"/>
	<xs:complexType name="GetItemsAwaitingFeedbackResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to GetItemsAwaitingFeedback.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemsAwaitingFeedback" type="ns:PaginatedTransactionArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items awaiting feedback.
								Returned only if there are items that do not yet
								have feedback.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetItemsAwaitingFeedback</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMemberMessages -->
	<xs:element name="GetMemberMessagesRequest" type="ns:GetMemberMessagesRequestType"/>
	<xs:complexType name="GetMemberMessagesRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a list of the messages buyers have posted about your
				active item listings.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddMemberMessagesAAQToBidder, AddMemberMessageAAQToPartner, AddMemberMessageRTQ,
					DeleteMyMessages, GetMyMessages, ReviseMyMessages, ReviseMyMessagesFolders
				</RelatedCalls>
				<SeeLink>
					<Title>Communication Between Members</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CommunicationBetweenMembers</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the item the message is about.
								&lt;br&gt;&lt;br&gt;
								For ASQ messages, either the ItemID, or a date range
								(specified with StartCreationTime and EndCreationTime),
								or both must be included. ItemID is otherwise ignored.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MailMessageType" type="ns:MessageTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The type of message. Note that GetMemberMessages does not return
								messages when this field is set to AskSellerQuestion.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<OnlyTheseValues>AskSellerQuestion, All</OnlyTheseValues>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MessageStatus" type="ns:MessageStatusTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The status of the message.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DisplayToPublic" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included in the request and set to True, only public messages (viewable
								in the Item listing) are returned. If omitted or set to False in the
								request, all messages (that match other filters in the request) are returned
								in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartCreationTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Used as beginning of date range filter. If specified,
								filters the returned messages to only those with a
								creation date greater than or equal to the specified
								date and time.
								&lt;br&gt;&lt;br&gt;
								For CEM messages, StartCreationTime and EndCreationTime
								must be provided.
								&lt;br&gt;&lt;br&gt;
								For ASQ messages, either the ItemID, or a date range
								(specified with StartCreationTime and EndCreationTime),
								or both must be included.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndCreationTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Used as end of date range filter. If specified, filters
								the returned messages to only those with a creation date
								less than or equal to the specified date and time.
								&lt;br&gt;&lt;br&gt;
								For CEM messages, StartCreationTime and EndCreationTime
								must be provided.
								&lt;br&gt;&lt;br&gt;
								For ASQ messages, either the ItemID, or a date range
								(specified with StartCreationTime and EndCreationTime),
								or both must be included.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Standard pagination argument used to reduce response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MemberMessageID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An ID that uniquely identifies the message for a given user to be retrieved.
								Used for the AskSellerQuestion notification only.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SenderID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An eBay ID that uniquely identifies a user. For
								GetMemberMessages, this is the sender of the message. If
								included in the request, returns only messages from the
								specified sender.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMemberMessages -->
	<xs:element name="GetMemberMessagesResponse" type="ns:GetMemberMessagesResponseType"/>
	<xs:complexType name="GetMemberMessagesResponseType">
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="MemberMessage" type="ns:MemberMessageExchangeArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The returned member messages. Returned if messages that meet the request criteria exist.
								Note that GetMemberMessages does not return
								messages when, in the request, the MailMessageType is AskSellerQuestion.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Shows the pagination of data returned by requests.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMoreItems" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether the response has more items.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMemberMessages</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMessagePreferences -->
	<xs:element name="GetMessagePreferencesRequest" type="ns:GetMessagePreferencesRequestType"/>
	<xs:complexType name="GetMessagePreferencesRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns a seller's Ask Seller a Question (ASQ) subjects, each in
				its own Subject node.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					SetMessagePreferences
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SellerID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the user to retrieve ASQ subjects for. This
								value must be specified in the request, but does not
								need to be the same user as the user making the
								request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMessagePreferences</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeASQPreferences" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, indicates that the ASQ subjects for the
								specified user should be returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMessagePreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMessagePreferences -->
	<xs:element name="GetMessagePreferencesResponse" type="ns:GetMessagePreferencesResponseType"/>
	<xs:complexType name="GetMessagePreferencesResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the ASQ subjects for the user specified in the request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ASQPreferences" type="ns:ASQPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns a seller's ASQ subjects, each in its own Subject
								node. If the seller has not customized the ASQ subjects
								using SetMessagePreferences, the call will return the
								current default values. Returned if
								IncludeASQPreferences = true was specified in the
								request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMessagePreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMyMessages -->
	<xs:element name="GetMyMessagesRequest" type="ns:GetMyMessagesRequestType"/>
	<xs:complexType name="GetMyMessagesRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves information about the messages sent to a given user.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Retrieves information about the messages sent to
					a user.
				</Summary>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>
					AddMemberMessageAAQToPartner, AddMemberMessageRTQ,
					AddMemberMessagesAAQToBidder, DeleteMyMessages, GetMemberMessages,
					ReviseMyMessages, ReviseMyMessagesFolders
				</RelatedCalls>
				<SeeLink>
					<Title>Communication Between Members</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CommunicationBetweenMembers</URL>
				</SeeLink>
				<SeeLink>
					<Title>Notifications for Buyers and Sellers</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=NotificationsForBuyersAndSellers</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AlertIDs" type="ns:MyMessagesAlertIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container was deprecated with 685 release. Alerts are now synonymous
								with Flagged messages.
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
					<!-- <CallInfo>
									<CallName>GetMyMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo> -->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MessageIDs" type="ns:MyMessagesMessageIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of one to 10 MessageID fields.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for a My Messages folder. If a FolderID is provided,
								only messages from the specified folder are returned in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The beginning of the date-range filter.
								Filtering takes into account the entire timestamp of when messages were sent.
								Messages expire after one year.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The end of the date-range filter. See StartTime
								(which is the beginning of the date-range filter).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExternalMessageIDs" type="ns:MyMessagesExternalMessageIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field is currently available on the US site. A container for IDs that
								uniquely identify messages for a given user. If provided at the time of message
								creation, this ID can be used to retrieve messages and will take precedence
								over message ID.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
						    <xs:documentation>
							Specifies how to create virtual pages in the returned list (such as total
							number of entries and total number of pages to return).
							Default for EntriesPerPage with GetMyMessages is 25.
						    </xs:documentation>
						    <xs:appinfo>
							<CallInfo>
								<CallName>GetMyMessages</CallName>
								<RequiredInput>No</RequiredInput>
							</CallInfo>
						    </xs:appinfo>
						</xs:annotation>
					</xs:element>
					 <xs:element name="IncludeHighPriorityMessageOnly" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If this field is included in the requst and set to True, only High Priority
								messages are returned in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyMessages</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
<!--\xmlschemas\ebl\APISchema\GetMyMessages\GetMyMessagesREquest.xsd-->	<!--  Call: GetMyMessages -->
  <xs:element name="GetMyMessagesResponse" type="ns:GetMyMessagesResponseType"/>
	<xs:complexType name="GetMyMessagesResponseType">
		<xs:annotation>
			<xs:documentation>
			Conains information about the messages sent to
			a user. Depending on the detail level, this
			information can include message counts,
			resolution and flagged status, message
			headers, and message text.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Summary" type="ns:MyMessagesSummaryType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Summary data for a given user's
								messages. This includes the numbers of
								new messages, flagged messages, and total messages.
								The amount and type of data returned is the same
								whether or not the request includes specific
								MessageIDs.
								Always/Conditionally returned logic assumes a
								detail level of ReturnMessages.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyMessages</CallName>
									<Details>DetailLevel: ReturnSummary</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Alerts" type="ns:MyMessagesAlertArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container was deprecated in 685 version. Alerts are now considered
								Flagged messages.
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
				<!--  <CallInfo>
									<CallName>GetMyMessages</CallName>
									<Details>DetailLevel: ReturnHeaders, ReturnMessages</Details>
									<Returned>Conditionally</Returned>
								</CallInfo> -->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Messages" type="ns:MyMessagesMessageArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the message information for each
								message specified in MessageIDs. The amount and
								type of information returned varies based on the
								requested detail level. Contains one
								MyMessagesMessageType object per message.
								Returned as an empty node if user has no
								messages.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyMessages</CallName>
									<Details>DetailLevel: ReturnHeaders, ReturnMessages</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMyeBayBuying -->
	<xs:element name="GetMyeBayBuyingRequest" type="ns:GetMyeBayBuyingRequestType"/>
	<xs:complexType name="GetMyeBayBuyingRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns items from the Buying section of the user's My eBay
				account, including items that the user is watching, bidding on, has
				won, has not won, and has made Best Offers on.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetItemsAwaitingFeedback, GetMyeBayReminders, GetMyeBaySelling</RelatedCalls>
				<SeeLink>
					<Title>My eBay</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=My_eBay</URL>
				</SeeLink>
				<TempInfo>DetailLevel</TempInfo>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="AbstractRequestType">
				<xs:sequence>
					<xs:element name="WatchList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items being watched by the user.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BidList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items on which the user has bid.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BestOfferList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items on which the user has placed Best Offers.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="WonList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items on which the use has bid.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LostList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items on which the user has bid on and lost.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FavoriteSearches" type="ns:MyeBaySelectionType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of searches that the user has saved in My eBay. Returned
								only if the user has saved searches.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FavoriteSellers" type="ns:MyeBaySelectionType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of favorite sellers that the user has saved in My eBay.
								Returned only if the user has saved a list of favorite sellers.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SecondChanceOffer" type="ns:MyeBaySelectionType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of second chance offers made by the user. Returned only
								if the user has made second chance offers.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BidAssistantList" type="ns:BidAssistantListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								<!-- This field is deprecated -->
								Indicates whether or not the Bid Assistant feature is being used. 
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
								<!-- <CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo> -->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedFromWonList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items the user has won, and subsequently deleted from
								their My eBay page.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedFromLostList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items (auctions) the user did not win and were
								subsequently deleted from their My eBay page.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BuyingSummary" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns a summary of the user's buying activity.
								&lt;br&gt;&lt;br&gt;
								Add a BuyingSummary element in
								the request with an Include field set to true to receive a BuyingSummary
								container in your response. Add a BuyingSummary element with an Include field
								set to false to exclude the BuyingSummary from your response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserDefinedLists" type="ns:MyeBaySelectionType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the user defined lists, which are lists created by the user in the eBay
								UI and filled with items, or sellers, or searches using the 
								"Add to List" feature.
								&lt;br&gt;&lt;br&gt;
								Set Include to true to return the default response set.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HideVariations" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the Variations node is omitted for all multi-variation
								listings in the response.
								If false, the Variations node is returned for all
								multi-variation listings in the response. &lt;br&gt;
								&lt;br&gt;
								Please note that if the seller includes a large number of
								variations in many listings, retrieving variations (setting this
								flag to false) may degrade the call's performance. Therefore,
								when this is false, you may need to reduce the total
								number of items you're requesting at once (by using other input
								fields, such as Pagination).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<RequiredInput>No</RequiredInput>
									<Default>false</Default>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMyeBayBuying -->
	<xs:element name="GetMyeBayBuyingResponse" type="ns:GetMyeBayBuyingResponseType"/>
	<xs:complexType name="GetMyeBayBuyingResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns items from All Buying or All Favorites in the user's My eBay account.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="AbstractResponseType">
				<xs:sequence>
					<xs:element name="BuyingSummary" type="ns:BuyingSummaryType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains a summary of the items the user has bid on. Returned at all detail
								levels.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="WatchList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the user is watching. Only returned if items exist that
								meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BidList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains all the items the buyer has bid on.
								Only returned if items exist that meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BestOfferList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the user has placed Best Offers on. Only returned if
								items exist that meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="WonList" type="ns:PaginatedOrderTransactionArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the user has bid on and won. Only returned if items
								exist that meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LostList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the user has bid on and lost. Only returned if items
								exist that meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FavoriteSearches" type="ns:MyeBayFavoriteSearchListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains a list of the user's favorite searches. Only returned if the
								user has Favorite Searches. The search name, search query, and search
								elements, such as QueryKeywords, SortOrder, and Condition are returned.
								&lt;br&gt;&lt;br&gt;
								You can paste the Search Query response, that comes back as a URL, into a browser
								to re-play the Favorite Search.
								&lt;br&gt;&lt;br&gt;
								The search elements that are returned by this call can be used as input
								for the Shopping Web Service FindItemsAdvanced request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FavoriteSellers" type="ns:MyeBayFavoriteSellerListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains a list of the user's favorite sellers. Only returned if items
								exist that meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SecondChanceOffer" type="ns:ItemType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Contains the list of second chance offers the user has received. Only
								returned if items exist that meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BidAssistantList" type="ns:BidGroupArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								<!-- This field is deprecated -->
								Contains the items that were bid on using the Bid Assistant feature.
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
								<!-- <CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo> -->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedFromWonList" type="ns:PaginatedOrderTransactionArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the buyer has bid on, won, and deleted from My eBay.
								Only returned if items exist that meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedFromLostList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the buyer has bid on, lost, and deleted from My eBay.
								Only returned if items exist that meet the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserDefinedList" type="ns:UserDefinedListType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Contains the items, searches, or sellers that the user has saved to this 
								list using the "Add to list" feature.  The name of the list is given by the 
								"Name" element. Returned only if UserDefineLists is specified in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayBuying</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMyeBayReminders -->
	<xs:element name="GetMyeBayRemindersRequest" type="ns:GetMyeBayRemindersRequestType"/>
	<xs:complexType name="GetMyeBayRemindersRequestType">
		<xs:annotation>
			<xs:documentation>
				Requests totals for the Buying and Selling reminders from the user's
				My eBay account.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					GetItemsAwaitingFeedback, GetMyeBayBuying, GetMyeBaySelling
				</RelatedCalls>
				<SeeLink>
					<Title>My eBay</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=My_eBay</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="AbstractRequestType">
				<xs:sequence>
					<xs:element name="BuyingReminders" type="ns:ReminderCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the type of buying reminders for which you want information.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayReminders</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingReminders" type="ns:ReminderCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the type of selling reminders for which you want information.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayReminders</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMyeBayReminders -->
	<xs:element name="GetMyeBayRemindersResponse" type="ns:GetMyeBayRemindersResponseType">
		<xs:annotation>
			<xs:documentation>
			Returns totals of various reminder types from the user's My eBay account.
			</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="GetMyeBayRemindersResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns totals of various reminder types from the user's My eBay account.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="AbstractResponseType">
				<xs:sequence>
					<xs:element name="BuyingReminders" type="ns:RemindersType" minOccurs="0">
						<xs:annotation>
								<xs:documentation>
									Contains the buying reminders in the user's My eBay account that match
									the request criteria.
								</xs:documentation>
								<xs:appinfo>
									<CallInfo>
										<CallName>GetMyeBayReminders</CallName>
										<Returned>Conditionally</Returned>
									</CallInfo>
								</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingReminders" type="ns:RemindersType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the selling reminders in the user's My eBay account that match
								the request criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBayReminders</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMyeBaySelling -->
	<xs:element name="GetMyeBaySellingRequest" type="ns:GetMyeBaySellingRequestType"/>
	<xs:complexType name="GetMyeBaySellingRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns items from the Selling section of the user's My eBay account,
				including items that the user is currently selling (the Active list),
				items that have bids, sold items, and unsold items.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>GetItemsAwaitingFeedback, GetMyeBayBuying, GetMyeBayReminders</RelatedCalls>
				<SeeLink>
					<Title>My eBay</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=My_eBay</URL>
				</SeeLink>
				<SeeLink>
					<Title>Managing Selling and Reminders with My eBay</Title>
					<URL>http://pages.ebay.com/help/myebay/manage-selling.html</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="AbstractRequestType">
				<xs:sequence>
					<xs:element name="ScheduledList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items the user has scheduled to sell but whose
								listings have not yet opened.
								&lt;br&gt;&lt;br&gt;
								Include and set the &lt;b&gt;ScheduledList.Include&lt;/b&gt; flag to 'true' to
								retrieve the default response set of &lt;b&gt;ScheduledList&lt;/b&gt; in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ActiveList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items the user is actively selling (the currently
								active listings).
								&lt;br&gt;&lt;br&gt;
								Include and set the &lt;b&gt;ActiveList.Include&lt;/b&gt; flag to 'true' to
								retrieve the default response set of &lt;b&gt;ActiveList&lt;/b&gt; in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SoldList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items the user has sold.
								&lt;br&gt;&lt;br&gt;
								Include and set the &lt;b&gt;SoldList.Include&lt;/b&gt; flag to 'true' to
								retrieve the default response set of &lt;b&gt;SoldList&lt;/b&gt; in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UnsoldList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items the user has listed, but whose listings
								have ended without being sold.
								&lt;br&gt;&lt;br&gt;
								Include and set the &lt;b&gt;UnsoldList.Include&lt;/b&gt; flag to 'true' to
								retrieve the default response set of &lt;b&gt;UnsoldList&lt;/b&gt; in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BidList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container is no longer applicable to &lt;b&gt;GetMyeBaySelling&lt;/b&gt;.
							</xs:documentation>
							<!-- <xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo> -->
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedFromSoldList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items the user sold, and then deleted from
								their My eBay page. Allowed values for DurationInDays are 0-60.
								&lt;br&gt;&lt;br&gt;
								Include and set the &lt;b&gt;DeletedFromSoldList.Include&lt;/b&gt; flag to 'true' to
								retrieve the default response set of &lt;b&gt;DeletedFromSoldList&lt;/b&gt; in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedFromUnsoldList" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the list of items the user either ended or did not sell, and
								subsequently were deleted them from their My eBay page. Allowed
								values for DurationInDays are 0-60.
								&lt;br&gt;&lt;br&gt;
								Include and set the &lt;b&gt;DeletedFromUnsoldList.Include&lt;/b&gt; flag to 'true' to
								retrieve the default response set of &lt;b&gt;DeletedFromUnsoldList&lt;/b&gt; in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingSummary" type="ns:ItemListCustomizationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns a summary of the user's buying activity.
								&lt;br&gt;&lt;br&gt;
								Include and set the &lt;b&gt;SellingSummary.Include&lt;/b&gt; flag to 'true' to
								retrieve the default response set of &lt;b&gt;SellingSummary&lt;/b&gt; in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HideVariations" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If 'true', the Variations node is omitted for all multi-variation
								listings in the response.
								If 'false', the Variations node is returned for all
								multi-variation listings in the response. &lt;br&gt;
								&lt;br&gt;
								Please note that if the seller includes a large number of
								variations in many listings, retrieving variations (setting this
								flag to 'false') may degrade the call's performance. Therefore,
								when this is 'false', you may need to reduce the total
								number of items you're requesting at once (by using other input
								fields, such as Pagination).
						  </xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
									<Default>false</Default>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetMyeBaySelling -->
	<xs:element name="GetMyeBaySellingResponse" type="ns:GetMyeBaySellingResponseType"/>
	<xs:complexType name="GetMyeBaySellingResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns summary and detail information about items the user is selling,
				items scheduled to sell, currently listed, sold, and closed but not sold.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="AbstractResponseType">
				<xs:sequence>
					<xs:element name="SellingSummary" type="ns:SellingSummaryType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains summary information about the items the user is selling.
							</xs:documentation>
							<xs:appinfo>
							<CallInfo>
								<CallName>GetMyeBaySelling</CallName>
								<Details>DetailLevel: none, ReturnAll</Details>
								<Returned>Always</Returned>
							</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ScheduledList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the user has scheduled for sale, but whose listings have
								not yet started.
							</xs:documentation>
							<xs:appinfo>
							<CallInfo>
								<CallName>GetMyeBaySelling</CallName>
								<Details>DetailLevel: none, ReturnAll</Details>
								<Returned>Conditionally</Returned>
							</CallInfo>
						</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ActiveList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the user is selling that have active listings.
							</xs:documentation>
							<xs:appinfo>
							<CallInfo>
								<CallName>GetMyeBaySelling</CallName>
								<Details>DetailLevel: none, ReturnAll</Details>
								<Returned>Conditionally</Returned>
							</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SoldList" type="ns:PaginatedOrderTransactionArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the user has sold.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UnsoldList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items whose listings have ended but that have not sold.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Summary" type="ns:MyeBaySellingSummaryType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains summary information about the items the user is selling.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BidList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container is no longer applicable to &lt;b&gt;GetMyeBaySelling&lt;/b&gt;.
							</xs:documentation>
							<!-- <xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo> -->
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedFromSoldList" type="ns:PaginatedOrderTransactionArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items the seller has sold and deleted from My eBay.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedFromUnsoldList" type="ns:PaginatedItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the items with listings that were ended or did not sell and have been deleted from My eBay.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetMyeBaySelling</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetNotificationPreferences -->
	<xs:element name="GetNotificationPreferencesRequest" type="ns:GetNotificationPreferencesRequestType"/>
	<xs:complexType name="GetNotificationPreferencesRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the requesting application's notification preferences. Details are only returned for events for which a
				preference has been set. For example, if you enabled notification for the EndOfAuction event and later disabled it,
				the GetNotificationPreferences response would cite the EndOfAuction event preference as Disabled. Otherwise, no
				details would be returned regarding EndOfAuction.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Working with Platform Notifications</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=PlatformNotifications</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="PreferenceLevel" type="ns:NotificationRoleCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the type of preferences to retrieve. For example, preferences can be associated with a user, with
								an application, or with events.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationPreferences</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetNotificationPreferences -->
	<xs:element name="GetNotificationPreferencesResponse"  type="ns:GetNotificationPreferencesResponseType"/>
	<xs:complexType name="GetNotificationPreferencesResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the requesting application's notification preferences.
				GetNotificationPreferences retrieves preferences that you have
				deliberately set. For example, if you enable the EndOfAuction event and
				then later disable it, the response shows the EndOfAuction event
				preference as Disabled. But if you have never set a preference for the
				EndOfAuction event, no EndOfAuction preference is returned at all.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ApplicationDeliveryPreferences" type="ns:ApplicationDeliveryPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies application-based event preferences that have been enabled.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeliveryURLName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies application delivery URL Name associated with this user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserDeliveryPreferenceArray" type="ns:NotificationEnableArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies user-based event preferences that have been enabled or disabled.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserData" type="ns:NotificationUserDataType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns user data for notification settings, such as set mobile phone.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EventProperty" type="ns:NotificationEventPropertyType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Contains names and values assigned to a notification event.
								Currently can only be set for wireless applications.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetNotificationsUsage -->
	<xs:element name="GetNotificationsUsageRequest" type="ns:GetNotificationsUsageRequestType"/>
	<xs:complexType name="GetNotificationsUsageRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves usage information about platform notifications for a given application.
				You can use this notification information to troubleshoot issues with platform
				notifications. You can call this up to 50 times per hour for a given application.
			</xs:documentation>
		<xs:appinfo>
			<SeeLink>
				<Title>Working with Platform Notifications</Title>
				<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=PlatformNotifications</URL>
			</SeeLink>
		</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the start date and time for which notification information
								will be retrieved. StartTime is optional. If no StartTime is specified,
								the default value of 24 hours prior to the call time is used. If no
								StartTime is specified or if an invalid StartTime is specified, date
								range errors are returned in the response. For a StartTime to be valid,
								it must be no more than 72 hours before the time of the call, it cannot
								be more recent than the EndTime, and it cannot be later than the time of
								the call. If an invalid StartTime is specified, the default value is
								used.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationsUsage</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the end date and time for which notification information
								will be retrieved. EndTime is optional. If no EndTime is specified,
								the current time (the time the call is made) is used. If no EndTime
								is specified or if an invalid EndTime is specified, date range errors
								are returned in the response. For an EndTime to be valid, it must be no
								more than 72 hours before the time the of the call, it cannot be before
								the StartTime, and it cannot be later than the time of the call. If an
								invalid EndTime is specified, the current time is used.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationsUsage</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies an item ID for which detailed notification information will be
								retrieved. ItemID is optional. If no ItemID is specified, the response
								will not include any individual notification details.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetNotificationsUsage</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetNotificationsUsage -->
	<xs:element name="GetNotificationsUsageResponse" type="ns:GetNotificationsUsageResponseType"/>
	<xs:complexType name="GetNotificationsUsageResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns an array of notifications sent to a given application identified by the appID
				(comes in the credentials). The result can be used by third-party developers troubleshoot
				issues with notifications.
				Zero, one or many notifications can be returned in the array. The set of notifications
				returned is limited to those that were sent between the StartTime and EndTime specified
				in the request. If StartTime or EndTime filters were not found in the request, then
				the response will contain the data for only one day (Now-1day). By default, maximum
				duration is limited to 3 days (Now-3days). These min (1day) and max(3days) applies
				to Notifications,MarkDownMarkUpHistory and NotificationStatistics.

				Notifications are sent only if the ItemID is included in the request. If there is no
				ItemID, then only Statistics and MarkDownMarkUpHistory information is included.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the start date and time for the notification information that is
								returned by this call. The oldest date allowed for this field is Now-3days.
								Default is Now-1day.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationsUsage</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the end date and time for the notification information that is
								returned by this call. The default is Now.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationsUsage</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NotificationDetailsArray" type="ns:NotificationDetailsArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								List of notification objects representing the notifications sent to an
								application for the given time period. It will only be returned if ItemID
								was specified in the input request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationsUsage</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MarkUpMarkDownHistory" type="ns:MarkUpMarkDownHistoryType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								List of objects representing MarkUp or MarkDown history for a given appID
								and for given StartTime and EndTime. This node will always be returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationsUsage</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NotificationStatistics" type="ns:NotificationStatisticsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Summary information about number of notifications that were successfully
								delivered, queued, failed, connection attempts made, connection timeouts,
								http errors for the given appID and given time period. By default, statistics
								for only one day (Now-1day) is included. Maximum time duration allowed is 3 days
								(Now-3days).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetNotificationsUsage</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetOrderTransactions -->
	<xs:element name="GetOrderTransactionsRequest" type="ns:GetOrderTransactionsRequestType"/>
	<xs:complexType name="GetOrderTransactionsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves information about one or more orders based on OrderIDs, ItemIDs, or SKU values. &amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>GetOrders, GetItemTransactions, GetSellerTransactions</RelatedCalls>
				<SeeLink>
					<Title>Basic Building Blocks</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=TransactionsEndOfAuction</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemTransactionIDArray" type="ns:ItemTransactionIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An array of one or more &lt;b&gt;ItemTransactionID&lt;/b&gt; containers. Each 
								&lt;b&gt;ItemTransactionID&lt;/b&gt; container identifies an order line item 
								to retrieve in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrderTransactions</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderIDArray" type="ns:OrderIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An array of one or more &lt;b&gt;OrderID&lt;/b&gt; containers. Each 
								&lt;b&gt;OrderID&lt;/b&gt; container identifies an order to retrieve in the response.
								Up to 20 orders (using 20 &lt;b&gt;OrderID&lt;/b&gt; containers) can be 
								retrieved with one &lt;b&gt;GetOrderTransactions&lt;/b&gt; call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrderTransactions</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Platform" type="ns:TransactionPlatformCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Name of the eBay co-branded site upon which the order line item was created.
								This will serve as a filter for the orders to get emitted in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrderTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeFinalValueFees" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether to include Final Value Fee (FVF) in the response. For most
								listing types, the Final Value Fee is returned in Transaction.FinalValueFee.
								The Final Value Fee is returned for each order line item (Transaction 
								container) for fixed-price listings. For all other listing
								types, the Final Value Fee is returned when the listing status is Completed.
								This value is not returned if the auction ended with Buy It Now.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrderTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetOrderTransactions -->
	<xs:element name="GetOrderTransactionsResponse" type="ns:GetOrderTransactionsResponseType"/>
	<xs:complexType name="GetOrderTransactionsResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to GetOrderTransactions request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="OrderArray" type="ns:OrderArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An array of Orders.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrderTransactions</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetOrders -->
	<xs:element name="GetOrdersRequest" type="ns:GetOrdersRequestType"/>
	<xs:complexType name="GetOrdersRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the orders for which the authenticated user is a participant, either as the buyer
				or the seller.&amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;. The call returns all the
				orders that meet the request specifications.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>AddOrder, GetItemTransactions, GetOrderTransactions</RelatedCalls>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=WorkingWithCombinedPayment</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="OrderIDArray" type="ns:OrderIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A container for eBay order IDs. If one or more order IDs are specified in this
								container, no other call-specific input fields are applicable.
								&lt;br&gt;&lt;br&gt;
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CreateTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The &lt;b&gt;CreateTimeFrom&lt;/b&gt; and &lt;b&gt;CreateTimeTo&lt;/b&gt; fields
								specify a date range for retrieving orders. The &lt;b&gt;CreateTimeFrom&lt;/b&gt; field is the
								starting date range. All eBay orders that were created within this date range are
								returned in the output. The maximum date range that may be specified with the
								&lt;b&gt;CreateTimeFrom&lt;/b&gt; and &lt;b&gt;CreateTimeTo&lt;/b&gt; fields is 90 
								days. &lt;b&gt;CreateTimeFrom&lt;/b&gt;/&lt;b&gt;CreateTimeTo&lt;/b&gt; date
								filters are ignored if the &lt;b&gt;NumberOfDays&lt;/b&gt; date filter is used in the request, or if
								one or more order IDs are passed in the request.
								&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CreateTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The &lt;b&gt;CreateTimeFrom&lt;/b&gt; and &lt;b&gt;CreateTimeTo&lt;/b&gt; fields specify a date range for retrieving
								orders. The &lt;b&gt;CreateTimeTo&lt;/b&gt; field is the ending date range. All eBay orders that were
								created within this date range are returned in the output. The maximum
								date range that may be specified with the &lt;b&gt;CreateTimeFrom&lt;/b&gt; and &lt;b&gt;CreateTimeTo&lt;/b&gt; fields
								is 90 days. If the &lt;b&gt;CreateTimeFrom&lt;/b&gt; field is used and the
								&lt;b&gt;CreateTimeTo&lt;/b&gt; field is omitted, the "TimeTo" value defaults to the present time or
								to 90 days past the &lt;b&gt;CreateTimeFrom&lt;/b&gt; value (if &lt;b&gt;CreateTimeFrom&lt;/b&gt; value is more than 90
								days in the past). &lt;b&gt;CreateTimeFrom&lt;/b&gt;/&lt;b&gt;CreateTimeTo&lt;/b&gt; date filters are ignored if the
								&lt;b&gt;NumberOfDays&lt;/b&gt; date filter is used in the request, or if one or more order IDs are
								passed in the request.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
									If a GetOrders call is made within a few seconds after the creation of a multiple
									line item order, the caller runs the risk of retrieving orders that are in an
									inconsistent state, since the order consolidation involved in a multi-line item order
									may not have been completed. For
									this reason, it is recommended that sellers include the
									&lt;b&gt;CreateTimeTo&lt;/b&gt; field in the call, and set its value to: &lt;i&gt;
									Current Time&lt;/i&gt; - 2 minutes.
								&lt;br&gt;&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderRole" type="ns:TradingRoleCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Filters the returned orders based on the role of the user. The user's role is
								either buyer or seller. If this field is used with a date filter, returned orders
								must satisfy both the date range and the OrderRole value.
								&lt;br&gt;
								Applicable to eBay.com and Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderStatus" type="ns:OrderStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Filters the returned orders by order status. For eBay orders, only the Active and
								Completed values are applicable. The Shipping value can be used for Half.com
								orders. If this field is used with a date filter, returned orders
								must satisfy both the date range and the OrderStatus value.
								&lt;br&gt;&lt;br&gt;
								To retrieve orders with a status of Inactive or Cancelled, you must specify
								the order IDs (OrderIDArray.OrderID). When you specify order IDs, no
								other filters may be used.
								&lt;br&gt;&lt;br&gt;
								For Half.com, you can get some, but not all orders.
								Orders on Half.com have different order status values from
								eBay orders. When you set ListingType to Half, set OrderStatus
								to Shipped. Otherwise, GetOrders may return incomplete information
								or have indeterminate results.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<OnlyTheseValues>Active, Completed, Shipped,Cancelled,Inactive</OnlyTheseValues>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingType" type="ns:ListingTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specify Half to retrieve Half.com orders.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
									Do not use this field if you are retrieving eBay orders.
									&lt;br&gt;&lt;br&gt;
									This field cannot be used as a listing type filter on eBay.com. If not
									provided, or if you specify any value other than Half, this field has
									no useful effect and the call retrieves eBay orders of all types. Also,
									you can't retrieve both eBay and Half.com orders in the same response.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<OnlyTheseValues>Half</OnlyTheseValues>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If many orders are
								available to retrieve, you may need to call GetOrders multiple times to retrieve all
								the data. Each result set is returned as a page of entries. Use the
								Pagination filters to control the maximum number of entries to
								retrieve per page (i.e., per call), the page number to retrieve, and
								other data.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ModTimeFrom and ModTimeTo fields specify a date range for retrieving
								existing orders that have been modified within this time window (for example,
								'Incomplete' status to 'Pending' status or 'Pending' status to 'Complete' status). The
								ModTimeFrom field is the starting date range. All eBay orders that were last
								modified within this date range are returned in the output. The maximum date
								range that may be specified with the ModTimeFrom and ModTimeTo fields is 30
								days. ModTimeFrom/ModTimeTo date filters are ignored if the
								CreateTimeFrom/CreateTimeTo or NumberOfDays date filters are used in the
								request, or if one or more order IDs are passed in the request.
								&lt;br&gt;&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ModTimeFrom and ModTimeTo fields specify a date range for retrieving
								existing orders that have been modified within this time window (for example,
								'Incomplete' status to 'Pending' status or 'Pending' status to 'Complete'
								status). The ModTimeTo field is the ending date range. All eBay orders that were
								last modified within this date range are returned in the output. The maximum
								date range that may be specified with the ModTimeFrom and ModTimeTo fields is 30
								days. If the ModTimeFrom field is used and the ModTimeTo field is omitted, the
								"TimeTo" value defaults to the present time (if ModTimeFrom value is less than
								30 days in the past) or to 30 days past the ModTimeFrom value.
								ModTimeFrom/ModTimeTo date filters are ignored if the
								CreateTimeFrom/CreateTimeTo or NumberOfDays date filters are used in the
								request, or if one or more order IDs are passed in the request.
								&lt;br&gt;&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NumberOfDays" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This filter specifies the number of days (24-hour periods) in the past to search
								for orders. All eBay orders that were either created or modified within this
								period are returned in the output. This field cannot be used in conjunction with
								the CreateTimeFrom/CreateTimeTo or ModTimeFrom/ModTimeTo date filters. This date 
								filter is ignored if one or more order IDs are passed in the request.
								&lt;br&gt;&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<min>1</min>
								<max>30</max>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeFinalValueFee" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether to include the Final Value Fee (FVF) for all Transaction objects in the
								response. The Final Value Fee is returned in Transaction.FinalValueFee. The Final
								Value Fee is assessed right after the creation of an eBay order line item.
							&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetOrders -->
	<xs:element name="GetOrdersResponse" type="ns:GetOrdersResponseType"/>
	<xs:complexType name="GetOrdersResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the set of orders that match the order IDs or filter criteria specified.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains information regarding the pagination of
								data, including the total number of pages and the total
								number of orders.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMoreOrders" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A true value indicates that there are more orders to be
								retrieved. Additional GetOrders calls with higher page numbers or more
								entries per page must be made to retrieve these orders. If false, no more
								orders are available or no orders match the request (based on the input
								filters).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderArray" type="ns:OrderArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The set of orders that match the order IDs or filter criteria specified.
								Also applicable to Half.com (only returns orders that have not been marked as shipped).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrdersPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the number of orders that can be
								returned per page of data (i.e., per call). This is the same value
								specified in the Pagination.EntriesPerPage input (or the default value, if
								EntriesPerPage was not specified). This is not necessarily the actual
								number of orders returned per page (see ReturnedOrderCountActual).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the page number of data returned in the response. 
								This is the same value specified in the
								Pagination.PageNumber input. If orders are returned, the first page is 1.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReturnedOrderCountActual" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the total number of orders returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetOrders</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductFamilyMembers -->
	<xs:element name="GetProductFamilyMembersRequest" type="ns:GetProductFamilyMembersRequestType"/>
	<xs:complexType name="GetProductFamilyMembersRequestType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- This supports an older ID-based format for 
				describing item specifics and product details.
				New applications should not use ID-based attributes. 
				Existing applications should be updated to remove all dependencies
				on ID-based attributes now. Instead, use FindProducts in 
				eBay's Shopping API to search for product details.  -->
			</xs:documentation>
			<xs:appinfo>
<!--
				<Summary>
					No longer applicable to any category.
				</Summary>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ProductSearch" type="ns:ProductSearchType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Specifies the ID of a product in the family to be retrieved,
								along with pagination and sorting instructions.
								ProductSearch is a required input.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
			<!--
								<CallInfo>
									<CallName>GetProductFamilyMembers</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
			-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductFamilyMembers -->
	<xs:element name="GetProductFamilyMembersResponse" type="ns:GetProductFamilyMembersResponseType"/>
	<xs:complexType name="GetProductFamilyMembersResponseType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- No longer applicable to any categories.  -->
			</xs:documentation>
			<xs:appinfo>
	<!--
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>Avoid</DeprecationDetails>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
				<EndOfLifeVersion>889</EndOfLifeVersion>
	-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="DataElementSets" type="ns:DataElementSetType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Container for one or more DataElement fields containing supplemental helpful data.
								A DataElement field is an HTML snippet that specifies hints for the user, help links,
								help graphics, and other supplemental information that varies per characteristics set.
								Usage of this information is optional and may require developers to inspect the information
								to determine how it can be applied in an application.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
			<!--
								<CallInfo>
									<CallName>GetProductFamilyMembers</CallName>
									<Returned>Always</Returned>
								</CallInfo>
			-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSearchResult" type="ns:ProductSearchResultType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Contains the attributes and summary product details for all products that match
								the product ID (or IDs) passed in the request.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
			<!--
								<CallInfo>
									<CallName>GetProductFamilyMembers</CallName>
									<Returned>Always</Returned>
								</CallInfo>
			-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductFinder -->
	<xs:element name="GetProductFinderRequest" type="ns:GetProductFinderRequestType"/>
	<xs:complexType name="GetProductFinderRequestType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- &lt;b&gt;No longer recommended.&lt;/b&gt; This supports an older ID-based format for
				describing item specifics and product details.
				New applications should not use ID-based attributes.
				Existing applications should be updated to remove all dependencies
				on ID-based attributes now. Instead, use FindProducts in
				eBay's Shopping API to search for product details.  -->
			</xs:documentation>
			<xs:appinfo>
<!--
				<Summary>
					No longer applicable to any category.
				</Summary>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
				<TempInfo>DetailLevel</TempInfo>
-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AttributeSystemVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A version of the product finder attribute definitions for the site.
								Typically, an application passes the version value that was returned the last
								time the application executed this call.
								Filter that causes the call to return only the Product Finders
								for which the attribute meta-data has changed since the specified version.
								The latest version value is not necessarily greater than the previous
								value that was returned. Therefore, when comparing versions, only
								compare whether the value has changed.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
   <!--
								<CallInfo>
									<CallName>GetProductFinder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
		-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductFinderID" type="xs:int" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A number that uniquely identifies a product finder. &lt;br&gt;
								&lt;br&gt;
								For sell-side searches, you can determine the
								product finder IDs for a category by calling GetCategory2CS.&lt;br&gt;
								&lt;br&gt;
								For buy-side searches, you can't use GetCategory2CS to reliably determine
								the product finder IDs for an eBay category.
								GetProductFinder may work for some attributes. Alternatively, you can
								use the pfid parameter from the URL of the Product Finder search page
								on the site you're interested in.
								See the Knowledge Base article referenced below for more details.&lt;br&gt;
								&lt;br&gt;
								Multiple categories can be mapped to the same product finder ID.
								You can pass zero or multiple IDs in the request. When IDs are specified, the call
								only returns product finder meta-data for the specified product finders.
								When no IDs are specified, the call returns all the current product finder
								meta-data available on the site.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
			<!--
								<CallInfo>
									<CallName>GetProductFinder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
			-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductFinder -->
	<xs:element name="GetProductFinderResponse" type="ns:GetProductFinderResponseType"/>
	<xs:complexType name="GetProductFinderResponseType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- No longer applicable to any category.  -->
			</xs:documentation>
			<xs:appinfo>
<!--
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AttributeSystemVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Current version of the product search page data for the site.
								This value changes each time changes are made to the search page data.
								The current version value is not necessarily greater than the previous
								value. Therefore, when comparing versions, only compare whether the
								value has changed.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
		<!--
								<CallInfo>
									<CallName>GetProductFinder</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo
	 	-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductFinderData" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A string containing a list of search attributes that can be used in a
								"Product Finder" style query, along with related meta-data. The meta-data
								specifies possible values of each attribute, the logic for presenting
								attributes to a user, and rules for validating the user's selections. For
								backward compatibility, this data is in the same XML format that was used
								in the Legacy XML API so that you can apply the same Product Finder XSL
								stylesheet to it. That is, individual elements are not described using the
								new eBay XML schema format. For information about each element in the
								ProductFinderData string, see the product finder model documentation in
								the eBay Web Services guide (see links below).&lt;br&gt;
								&lt;br&gt;
								Because this is returned as a string, the XML markup is escaped with
								character entity references (e.g., &amp;amp;lt;eBay&amp;amp;gt;&amp;amp;lt;ProductFinders&amp;amp;gt;...).
								See the appendices in the eBay Web Services guide for general information about
								string data types.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
	<!--
								<CallInfo>
									<CallName>GetProductFinder</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
	-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductFinderXSL -->
	<xs:element name="GetProductFinderXSLRequest" type="ns:GetProductFinderXSLRequestType"/>
	<xs:complexType name="GetProductFinderXSLRequestType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- &lt;b&gt;No longer recommended.&lt;/b&gt; This supports an older ID-based format for 
				describing item specifics and product details.
				Most eBay categories no longer support ID-based attributes.
				The remaining categories (e.g., US eBay Motors) will drop support 
				for ID-based attributes by May 2012. 
				New applications should not use ID-based attributes. 
				Existing applications should be updated to remove all dependencies
				on ID-based attributes now. Instead, use FindProducts in 
				eBay's Shopping API to search for product details.&lt;br&gt;
				&lt;br&gt;
				Retrieves the Product Finder XSL stylesheet. Apply the stylesheet
				to the XML returned from a call to GetProductFinder to render a
				form that lets a user form a multi-attribute query against eBay
				catalog data. See the Developer's Guide for an overview of Pre-
				filled Item Information and information on searching for catalog
				products.  -->
			</xs:documentation>
			<xs:appinfo>
<!--
				<Summary>
					No longer applicable to any category.
				</Summary>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
				<TempInfo>DetailLevel</TempInfo>
	
	-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="FileName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								The name of the XSL file to retrieve. If not specified, the call
								returns the latest versions of all available XSL files.
								Currently, this call only retrieves the product_finder.xsl file.
								FileName is an optional input.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
			<!--
								<CallInfo>
									<CallName>GetProductFinderXSL</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
			-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FileVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								The desired version of the XSL file. Required if FileName is specified.
								If not specified, the call returns the latest versions of all
								available XSL files that could be returned by the call.
								(Currently, this call only retrieves the product_finder.xsl file.)
								This is not a filter for retrieving changes to the XSL file.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
		<!--
								<CallInfo>
									<CallName>GetProductFinderXSL</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
		-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductFinderXSL -->
	<xs:element name="GetProductFinderXSLResponse" type="ns:GetProductFinderXSLResponseType"/>
	<xs:complexType name="GetProductFinderXSLResponseType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- No longer applicable to any category.  -->
			</xs:documentation>
			<xs:appinfo>
	<!--
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
	-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="XSLFile" type="ns:XSLFileType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Child elements specify data related to one XSL file.
								In theory, multiple XSLFile objects can be returned.
								Currently, this call only retrieves the product_finder.xsl file.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
	<!--
								<CallInfo>
									<CallName>GetProductFinderXSL</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
	-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductSearchPage -->
	<xs:element name="GetProductSearchPageRequest" type="ns:GetProductSearchPageRequestType"/>
	<xs:complexType name="GetProductSearchPageRequestType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- &lt;b&gt;No longer recommended.&lt;/b&gt; This supports an older ID-based format for 
				describing item specifics and product details.
				New applications should not use ID-based attributes. 
				Existing applications should be updated to remove all dependencies
				on ID-based attributes now. Instead, use FindProducts in 
				eBay's Shopping API to search for product details.  -->
			</xs:documentation>
			<xs:appinfo>
	<!--
				<Summary>
					No longer applicable to any category.
				</Summary>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
				<TempInfo>DetailLevel</TempInfo>
	-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AttributeSystemVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A version of the search page definitions for the site. Typically, an
								application passes the version value that was returned the last time the
								application executed this call. Filter that causes the call to return only
								the search pages for which the attribute meta-data has changed since the
								specified version. The latest version value is not necessarily greater
								than the previous value that was returned. Therefore, when comparing
								versions, only compare whether the value has changed.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
	<!--
								<CallInfo>
									<CallName>GetProductSearchPage</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
		
		-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AttributeSetID" type="xs:int" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A characteristic set ID that is associated with a
								catalog-enabled category that supports product search pages.
								You can pass an array of these IDs in the request.
								Each characteristic set corresponds to a level in the
								eBay category hierarchy at which all items share common characteristics.
								Multiple categories can be mapped to the same characteristic set.
								Each ID is used as a filter to limit the response content to fewer
								characteristic sets. When IDs are specified, the call only returns
								search page data for the corresponding characteristic sets.
								When no IDs are specified, the call returns all the current
								search page data in the system.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
		<!--
								<CallInfo>
									<CallName>GetProductSearchPage</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
		-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductSearchPage -->
	<xs:element name="GetProductSearchPageResponse" type="ns:GetProductSearchPageResponseType"/>
	<xs:complexType name="GetProductSearchPageResponseType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- No longer applicable to any categories.  -->
			</xs:documentation>
			<xs:appinfo>
	<!--
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
	-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AttributeSystemVersion" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Current version of the product search page data for the site.
								This value changes each time changes are made to the search page data.
								The current version value is not necessarily greater than the previous
								value. Therefore, when comparing versions, only compare whether the
								value has changed.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
				<!--
								<CallInfo>
									<CallName>GetProductSearchPage</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
				-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSearchPage" type="ns:ProductSearchPageType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A list of catalog search criteria and sort keys associated with a catalog-enabled category,
								plus supplemental information to help the seller understand how to make selections.
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
					<!--
								<CallInfo>
									<CallName>GetProductSearchPage</CallName>
									<Details>DetailLevel: ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
					-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductSearchResults -->
	<xs:element name="GetProductSearchResultsRequest" type="ns:GetProductSearchResultsRequestType"/>
	<xs:complexType name="GetProductSearchResultsRequestType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- &lt;b&gt;No longer recommended.&lt;/b&gt; This supports an older ID-based format for 
				describing item specifics and product details.
				New applications should not use ID-based attributes. 
				Existing applications should be updated to remove all dependencies
				on ID-based attributes now. Instead, use FindProducts in 
				eBay's Shopping API to search for product details.  -->
			</xs:documentation>
			<xs:appinfo>
<!--
				<Summary>
					No longer applicable to any category.
				</Summary>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
 -->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ProductSearch" type="ns:ProductSearchType"  minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Specifies the keywords or attributes that make up the product query, with
								pagination instructions. ProductSearch is a required input. To search for
								multiple different products at the same time (i.e., to perform a batch
								search), pass in multiple ProductSearch properties.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
			<!--
								<CallInfo>
									<CallName>GetProductSearchResults</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
			-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductSearchResults -->
	<xs:element name="GetProductSearchResultsResponse" type="ns:GetProductSearchResultsResponseType"/>
	<xs:complexType name="GetProductSearchResultsResponseType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!-- No longer applicable to any category.  -->
			</xs:documentation>
			<xs:appinfo>
	<!--
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
	-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="DataElementSets" type="ns:DataElementSetType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Container for one or more DataElement fields containing supplemental
								helpful data. A DataElement field is an HTML snippet that specifies hints
								for the user, help links, help graphics, and other supplemental
								information that varies per characteristic set. Usage of this information
								is optional and may require you to inspect the information to determine
								how it can be applied in an application. Also returned with warnings when
								no matches are found.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
		<!--
								<CallInfo>
									<CallName>GetProductSearchResults</CallName>
									<Returned>Always</Returned>
								</CallInfo>
		-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSearchResult" type="ns:ProductSearchResultType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Contains the attributes and product details that match the attributes or
								query keywords passed in the request. Always returned when product search
								results are found.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
		<!--
								<CallInfo>
									<CallName>GetProductSearchResults</CallName>
									<Returned>Always</Returned>
								</CallInfo>
		-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductSellingPages -->
	<xs:element name="GetProductSellingPagesRequest" type="ns:GetProductSellingPagesRequestType"/>
	<xs:complexType name="GetProductSellingPagesRequestType">
		<xs:annotation>
			<xs:documentation>
				his type is deprecated as the call is no longer available.
				<!--  &lt;b&gt;No longer recommended.&lt;/b&gt; This supports an older ID-based format for 
				describing item specifics and product details. 
				New applications should not use ID-based attributes. 
				Existing applications should be updated to remove all dependencies
				on ID-based attributes now. Instead, use FindProducts in 
				eBay's Shopping API to search for product details. -->
			</xs:documentation>
			<xs:appinfo>
<!--
				<Summary>
					No longer applicable to any category. 
				</Summary>
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="UseCase" type="ns:ProductUseCaseCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								Specifies the context in which the call is being executed, which will imply
								certain validation rules. Use this property to make sure you retrieve the
								appropriate version of product information and attribute meta-data
								when you are listing, revising, or relisting an item with Pre-filled Item Information.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
					<!--
								<CallInfo>
									<CallName>GetProductSellingPages</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
					-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Product" type="ns:ProductType"  minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A catalog product identifies a prototype description
								of a well-known type of item, such as a popular book.
								As this call supports batch requests, you can pass in an array of products
								to retrieve data for several products at the same time.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
					<!--
								<CallInfo>
									<CallName>GetProductSellingPages</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
				-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetProductSellingPages -->
	<xs:element name="GetProductSellingPagesResponse" type="ns:GetProductSellingPagesResponseType"/>
	<xs:complexType name="GetProductSellingPagesResponseType">
		<xs:annotation>
			<xs:documentation>
				This type is deprecated as the call is no longer available.
				<!--  No longer applicable to any category. -->
			</xs:documentation>
			<xs:appinfo>
		<!--
				<DeprecationVersion>773</DeprecationVersion>
				<DeprecationDetails>NoOp</DeprecationDetails>
				<EndOfLifeVersion>889</EndOfLifeVersion>
				<UseInstead>FindProducts (Shopping API)</UseInstead>
		-->
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ProductSellingPagesData" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						<!-- This field is deprecated -->
								A string containing a list of all the attributes that are applicable
								to the products specified in the request, along with related meta-data.
								The meta-data specifies the pre-filled values of each attribute, the
								possible values of attributes that are not pre-filled, the logic for presenting
								the attributes to a user, and rules for validating the user's selections.
								&lt;br&gt;&lt;br&gt;
								For backward compatibility, this data is in
								the same XML format that was used in the Legacy XML API so that you can
								apply the same Item Specifics XSL stylesheet to it. That is, individual
								elements are not described using the unified schema format.
								&lt;br&gt;&lt;br&gt;
								The data is based on the GetAttributesCS response (AttributeData), with
								additional information that is specific to catalog products.
								Product and attribute information is nested within a set of Product tags.
								The product-specific data is merged into the attribute data so that the same
								XSL stylesheet used to render the results of GetAttributeCS can be used to render
								catalog product data. See GetAttributesXSL.
								&lt;br&gt;&lt;br&gt;
								See the Attribute Meta-Data Model section of the eBay Web Services guide
								for information about each element in the ProductSellingPagesData string.
								&lt;br&gt;&lt;br&gt;
								Because the content is returned as a string, the XML markup elements are escaped with
								character entity references (e.g.,&amp;amp;lt;eBay&amp;amp;gt;&amp;amp;lt;Attributes&amp;amp;gt;...).
								See the appendices in the eBay Web Services guide for general information about
								string data types.
							</xs:documentation>
							<xs:appinfo>
							<NoCalls/>
					<!--
								<CallInfo>
									<CallName>GetProductSellingPages</CallName>
									<Returned>Always</Returned>
								</CallInfo>
					-->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetPromotionRules -->
	<xs:element name="GetPromotionRulesRequest" type="ns:GetPromotionRulesRequestType"/>
	<xs:complexType name="GetPromotionRulesRequestType">
		<xs:annotation>
			<xs:documentation>
				&lt;b&gt;No longer recommended.&lt;/b&gt; eBay Store Cross Promotions are no
				longer supported in the Trading API. Retrieves all promotion rules associated with the specified item or store category.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Cross-Promotions</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CrossPromotionsChapter</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique ID of the item for which to retrieve promotion rules.
								Mutually exclusive with StoreCategoryID.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetPromotionRules</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StoreCategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique ID of the store category for which to retrieve promotion rules.
								Mutually exclusive with ItemID.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetPromotionRules</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionMethod" type="ns:PromotionMethodCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The type of promotion. (CrossSell: items that are related to or
								useful in combination with this item. UpSell: items that are more
								expensive than or of higher quality than this item.)
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetPromotionRules</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetPromotionRules -->
	<xs:element name="GetPromotionRulesResponse" type="ns:GetPromotionRulesResponseType"/>
	<xs:complexType name="GetPromotionRulesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns all promotion rules associated with the specified item or store category. 
				<strong>Note:</strong> eBay Store Cross Promotions are no longer supported in the 
				Trading API.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PromotionRuleArray" type="ns:PromotionRuleArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation> 
								An array of promotion rules associated with the item or store category
								specified in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetPromotionRules</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetPromotionalSaleDetails -->
	<xs:element name="GetPromotionalSaleDetailsRequest" type="ns:GetPromotionalSaleDetailsRequestType"/>
	<xs:complexType name="GetPromotionalSaleDetailsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves information about promotional sales set up by an eBay store owner
				(the authenticated caller).
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					GetPromotionRules, SetPromotionalSale, SetPromotionalSaleListings
				</RelatedCalls>
				<SeeLink>
					<Title>Putting Store Items on Sale</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=PuttingItemsOnSale</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="PromotionalSaleID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the promotional sale about which you want information. If you do
								not specify this field, then all promotional sales for the seller making
								the call are returned or only those promotional sales matching the
								specified promotional sale status filter, PromotionalSaleStatus.
								&lt;br&gt;&lt;br&gt;
								If PromotionalSaleID and PromotionalSaleStatus are both specified, the
								single promotional sale specified by ID is returned only if its status
								matches the specified status filter.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetPromotionalSaleDetails</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionalSaleStatus" type="ns:PromotionalSaleStatusCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the promotional sales to return, based upon their status. For
								example, specify "Scheduled" to retrieve only promotional sales with a
								Status of Scheduled. If you want to retrieve promotional sales for more
								than one status, you can repeat the field with an additional status value,
								such as Active.
								&lt;br&gt;&lt;br&gt;
								If this field is used together with PromotionalSaleID, the single
								promotional sale specified by ID is returned only if its status
								matches the specified status filter.
								&lt;br&gt;&lt;br&gt;
								If neither field is used, all of the seller's promotional sales are
								returned, regardless of status.
							</xs:documentation>
							<xs:appinfo>
								<Default>No filtering</Default>
								<CallInfo>
									<CallName>GetPromotionalSaleDetails</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetPromotionalSaleDetails -->
	<xs:element name="GetPromotionalSaleDetailsResponse" type="ns:GetPromotionalSaleDetailsResponseType"/>
	<xs:complexType name="GetPromotionalSaleDetailsResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains information about promotional sales. This call
				is part of the Promotional Price Display feature.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PromotionalSaleDetails" type="ns:PromotionalSaleArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains information about a promotional sale or sales. If you did not 
								specify a PromotionalSaleID in the request, then all promotional sales
								for the seller are returned. Promotional sales enable sellers to add 
								discounts and/or free shipping to items. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetPromotionalSaleDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerDashboard -->
	<xs:element name="GetSellerDashboardRequest" type="ns:GetSellerDashboardRequestType"/>
	<xs:complexType name="GetSellerDashboardRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a brief summary of the requester's status as an eBay seller.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetAccount, GetFeedback, GetUser</RelatedCalls>
				<SeeLink>
					<Title>About Your Seller Dashboard (eBay US online help)</Title>
					<URL>http://pages.ebay.com/help/myebay/seller-dashboard.html</URL>
				</SeeLink>
				<SeeLink>
					<Title>Zum Thema Verkaufer-Cockpit (eBay Germany online help)</Title>
					<URL>http://pages.ebay.de/help/myebay/seller-dashboard.html</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerDashboard -->
	<xs:element name="GetSellerDashboardResponse" type="ns:GetSellerDashboardResponseType"/>
	<xs:complexType name="GetSellerDashboardResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns a brief summary of the requester's status as an eBay seller. The status
				information can help an eBay seller monitor their selling performance and keep
				their account in good standing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SearchStanding" type="ns:SearchStandingDashboardType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides information about the visibility level you have earned for your
								listings. The higher your search standing rating, the higher your items
								will be placed in search results sorted by Best Match. Because your search
								standing rating is directly tied to your customer service record, this
								rating is an important way that eBay rewards you as a good seller--it
								encourages you to give buyers the best possible shopping experience.
								&lt;br&gt;&lt;br&gt;
								This element is not returned for all sites. Beginning at the end of 2009, eBay
								stopped returning it for sellers registered on several large sites, including
								the US, German, and UK sites.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerDashboard</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
								<SeeLink>
									<Title>About Your Seller Dashboard: Search Standing</Title>
									<URL>http://pages.ebay.com/help/myebay/seller-dashboard.html#standing</URL>
								</SeeLink>
								<SeeLink>
									<Title>Zum Thema Verkaeufer-Cockpit: Platzierung in der Suche</Title>
									<URL>http://pages.ebay.de/help/myebay/seller-dashboard.html#standing</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerFeeDiscount" type="ns:SellerFeeDiscountDashboardType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides information about the PowerSeller discount level you have earned,
								if any. As a PowerSeller, you can earn discounts on your monthly invoice
								Final Value Fees based on how well you're rated as a seller. Only returned
								for members of the eBay US or Canada PowerSeller program.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerDashboard</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
								<SeeLink>
									<Title>About Your Seller Dashboard: PowerSeller Discount</Title>
									<URL>http://pages.ebay.com/help/myebay/seller-dashboard.html#discount</URL>
								</SeeLink>
								<SeeLink>
									<Title>Zum Thema Verkaeufer-Cockpit: PowerSeller-Rabatt</Title>
									<URL>http://pages.ebay.de/help/myebay/seller-dashboard.html#discount</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PowerSellerStatus" type="ns:PowerSellerDashboardType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides information about your PowerSeller status, such as whether or not
								you meet the PowerSeller requirements. Your PowerSeller status directly
								affects your discount (SellerFeeDiscount).
								&lt;br&gt;&lt;br&gt;
								For eBay Germany and France, you must be a registered business seller to
								see your PowerSeller status.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerDashboard</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
								<SeeLink>
									<Title>About Your Seller Dashboard: PowerSeller Status</Title>
									<URL>http://pages.ebay.com/help/myebay/seller-dashboard.html#status</URL>
								</SeeLink>
								<SeeLink>
									<Title>PowerSeller Benefits and Requirements</Title>
									<URL>http://pages.ebay.com/services/buyandsell/welcome.html</URL>
								</SeeLink>
								<SeeLink>
									<Title>Zum Thema Verkaeufer-Cockpit: PowerSeller-Status</Title>
									<URL>http://pages.ebay.de/help/myebay/seller-dashboard.html#status</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PolicyCompliance" type="ns:PolicyComplianceDashboardType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Rating on how well you are following eBay rules and policies in your selling
								practices, and alerts you if your account or listings have any policy
								violations.
								&lt;br&gt;&lt;br&gt;
								eBay's policies and rules are guidelines that help to create a safe, fair,
								and enjoyable trading environment for all eBay members. If you violate
								certain policies, your account can be restricted without notice. This is true
								even if your status shows a good level of policy compliance. Because of this,
								understanding and following eBay's policies can help you to avoid
								restrictions on your account. Policy compliance directly affects your
								PowerSeller status.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerDashboard</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>About Your Seller Dashboard: Policy Compliance</Title>
									<URL>http://pages.ebay.com/help/myebay/seller-dashboard.html#compliance</URL>
								</SeeLink>
								<SeeLink>
									<Title>Rules for Sellers</Title>
									<URL>http://pages.ebay.com/help/policies/seller-rules-overview.html</URL>
								</SeeLink>
								<SeeLink>
									<Title>Zum Thema Verkaeufer-Cockpit: Einhaltung der Grundsaetze</Title>
									<URL>http://pages.ebay.de/help/myebay/seller-dashboard.html#compliance</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BuyerSatisfaction" type="ns:BuyerSatisfactionDashboardType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Rates your level of customer service. This information helps you to keep
								track of how well you are providing members with positive buying
								experiences.
								&lt;br&gt;&lt;br&gt;
								This element is not returned for all sites. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerDashboard</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
								<SeeLink>
									<Title>About Your Seller Dashboard: Buyer Satisfaction</Title>
									<URL>http://pages.ebay.com/help/myebay/seller-dashboard.html#buyer</URL>
								</SeeLink>
								<SeeLink>
									<Title>Zum Thema Verkaeufer-Cockpit: Kaeuferzufriedenheit</Title>
									<URL>http://pages.ebay.de/help/myebay/seller-dashboard.html#buyer</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerAccount" type="ns:SellerAccountDashboardType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The status of your latest eBay invoice. Includes any alerts issued to your
								account to help you identify possible problems.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerDashboard</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>About Your Seller Dashboard: Account Status</Title>
									<URL>http://pages.ebay.com/help/myebay/seller-dashboard.html#account</URL>
								</SeeLink>
								<SeeLink>
									<Title>Zum Thema Verkaeufer-Cockpit: Kontostand</Title>
									<URL>http://pages.ebay.de/help/myebay/seller-dashboard.html#account</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Performance" type="ns:PerformanceDashboardType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Provides information about the seller's performance within different eBay
								regions. A seller's performance rating can be Top-Rated, Above Standard,
								Standard, and Below Standard.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerDashboard</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>Top-Rated Seller Status</Title>
									<URL>http://pages.ebay.com/sell/July2009Update/Details/index.html#1-2</URL>
								</SeeLink>
								<SeeLink>
									<Title>About Your Seller Dashboard: Performance Status</Title>
									<URL>http://pages.ebay.com/help/myebay/seller-dashboard.html#performance</URL>
								</SeeLink>
								<SeeLink>
									<Title>Zum Thema Verkaeufer-Cockpit: Leistung</Title>
									<URL>http://pages.ebay.de/help/myebay/seller-dashboard.html#performance</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerEvents -->
	<xs:element name="GetSellerEventsRequest" type="ns:GetSellerEventsRequestType"/>
	<xs:complexType name="GetSellerEventsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves price changes, item revisions, description revisions,
				and other changes that have occurred within the last 48 hours
				related to a seller's eBay listings.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<SeeLink>
					<Title>Working with Seller Events</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=WorkingWithSellerEvents</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="UserID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								eBay user ID for the seller whose events are to be returned.
								If not specified, retrieves events for the user identified by
								the authentication token passed in the request. Note that since user information is anonymous to everyone except the bidder and the seller (during an active auction), only sellers looking for information about
								their own listings and bidders who know the user IDs of their sellers
								will be able to make this API call successfully.
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>Working with Anonymous User Information</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=AnonymousUserInfo</URL>
								</SeeLink>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Describes the earliest (oldest) time to use in a time range filter based
								on item start time. Must be specified if StartTimeTo is specified. Either
								the StartTimeFrom, EndTimeFrom, or ModTimeFrom filter must be specified.
								If you do not specify the correspoding To filter,
								it is set to the time you make the call.
								For better results, the time period you use should be less than 48 hours.
								If 3000 or more items are found, use a smaller time range.&lt;br&gt;
								&lt;br&gt;
								Include a 2-minute, overlapping buffer between requests.
								For example, if StartTimeTo was 6:58 in a prior request,
								the current request should use 6:56 in StartTimeFrom
								(e.g., use ranges like 5:56-6:58, 6:56-7:58, 7:56-8:58).
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>KB article: Best Practices for GetSellerEvents and GetSellerTransactions</Title>
									<URL>http://ebay.custhelp.com/cgi-bin/ebay.cfg/php/enduser/std_adp.php?p_faqid=222</URL>
								</SeeLink>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Describes the latest (most recent) date to use in a time range filter
								based on item start time. If you specify the corresponding From filter,
								but you do not include StartTimeTo, the StartTimeTo is set to
								the time you make the call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Describes the earliest (oldest) date to use in a time range filter based
								on item end time. Must be specified if EndTimeTo is specified. Either
								the StartTimeFrom, EndTimeFrom, or ModTimeFrom filter must be specified.
								If you do not specify the correspoding To filter,
								it is set to the time you make the call.&lt;br&gt;
								&lt;br&gt;
								For better results, the time range you use should be less than 48 hours.
								If 3000 or more items are found, use a smaller time range.&lt;br&gt;
								&lt;br&gt;
								Include a 2-minute, overlapping buffer between requests.
								For example, if EndTimeTo was 6:58 in a prior request,
								the current request should use 6:56 in EndTimeFrom
								(e.g., use ranges like 5:56-6:58, 6:56-7:58, 7:56-8:58).
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>KB article: Best Practices for GetSellerEvents and GetSellerTransactions</Title>
									<URL>http://ebay.custhelp.com/cgi-bin/ebay.cfg/php/enduser/std_adp.php?p_faqid=222</URL>
								</SeeLink>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Describes the latest (most recent) date to use in a time range filter
								based on item end time. If you specify the corresponding From filter,
								but you do not include EndTimeTo, then EndTimeTo is set
								to the time you make the call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Describes the earliest (oldest) date to use in a time range filter based
								on item modification time. Must be specified if ModTimeTo is specified. Either
								the StartTimeFrom, EndTimeFrom, or ModTimeFrom filter must be specified.
								If you do not specify the correspoding To filter,
								it is set to the time you make the call.&lt;br&gt;
								&lt;br&gt;
								Include a 2-minute, overlapping buffer between requests.
								For example, if ModTimeTo was 6:58 in a prior request,
								the current request should use 6:56 in ModTimeFrom
								(e.g., use ranges like 5:56-6:58, 6:56-7:58, 7:56-8:58).
								&lt;br&gt;&lt;br&gt;
								For better results, the time range you use should be less than 48 hours.
								If 3000 or more items are found, use a smaller time range.
								&lt;br&gt;&lt;br&gt;
								If an unexpected item is returned (including an old item
								or an unchanged active item), please ignore the item.
								Although a maintenance process may have triggered a change in the modification time,
								item characteristics are unchanged.
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>KB article: Best Practices for GetSellerEvents and GetSellerTransactions</Title>
									<URL>http://ebay.custhelp.com/cgi-bin/ebay.cfg/php/enduser/std_adp.php?p_faqid=222</URL>
								</SeeLink>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Describes the latest (most recent) date and time to use in a time range filter
								based on the time an item's record was modified. If you specify
								the corresponding From filter, but you do not include ModTimeTo,
								then ModTimeTo is set to the time you make the call.
								Include a 2-minute buffer between the current time and
								the ModTimeTo filter.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NewItemFilter" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Default is true. If true, response includes only items that have been modified
								within the ModTime range. If false, response includes all items.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeWatchCount" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether to include WatchCount in Item nodes returned. WatchCount
								is the number of watches buyers have placed on the item from their My eBay
								accounts.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeVariationSpecifics" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether to force the response to include
								variation specifics for multi-variation listings. &lt;br&gt;
								&lt;br&gt;
								If false (or not specified), eBay keeps the response as small as
								possible by not returning Variation.VariationSpecifics.
								It only returns Variation.SKU as an identifier
								(along with the variation price and other selling details).
								If the variation has no SKU, then Variation.VariationSpecifics
								is returned as the variation's unique identifier.&lt;br&gt;
								&lt;br&gt;
								If true, Variation.VariationSpecifics is returned.
								(Variation.SKU is also returned, if the variation has a SKU.)
								This may be useful for applications that don't track variations
								by SKU.&lt;br&gt;
								&lt;br&gt;
								Ignored when HideVariations=true.&lt;br&gt;
								&lt;br&gt;
								Please note that if the seller includes a large number of
								variations in many listings, using this flag may degrade the
								call's performance. Therefore, when you use this flag, you may
								need to reduce the total number of items you're requesting at
								once. For example, you may need to use shorter time ranges in
								the EndTime, StartTime, or ModTime filters.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HideVariations" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether to force the response to hide
								variation details for multi-variation listings.&lt;br&gt;
								&lt;br&gt;
								If false (or not specified), eBay returns variation details (if
								any). In this case, the amount of detail can be controlled by
								using IncludeVariationSpecifics.&lt;br&gt;
								&lt;br&gt;
								If true, variation details are not returned (and
								IncludeVariationSpecifics has no effect). This may be useful for
								applications that use other calls, notifications, alerts,
								or reports to track price and quantity details.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerEvents -->
	<xs:element name="GetSellerEventsResponse" type="ns:GetSellerEventsResponseType"/>
	<xs:complexType name="GetSellerEventsResponseType">
		<xs:annotation>
			<xs:documentation>
					Contains the items returned by the call. Items for which a seller event has
					occurred (and that meet any filters specified as input) are returned in an
					ItemArrayType object, within which are zero, one, or multiple ItemType objects.
					Each ItemType object contains the detail data for one item listing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="TimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
											Indicates the latest (most recent) date for any date-based filtering specified as
											input. Specifically, this field contains the value you specified in the StartTimeTo, EndTimeTo, or ModTimeTo filter, if you used a time filter in the request. If no time filter was specified, TimeTo returns the current time.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemArray" type="ns:ItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Collection of items whose last modified time matches
								the filters specified in the request. 
								Returns empty if no items were modified within the 
								time range of the request. 
								If 1 to 2999 items are returned, then the results are 
								complete. If 3000 or more items are returned, it usually means 
								additional items exist within the time range you requested, 
								but they were not all returned. To retrieve complete results,
								use a smaller time range in the request so that fewer than 
								3000 are returned per response. 
							</xs:documentation>
							<xs:appinfo>
							<SeeLink>
								<Title>KB article: Best Practices for GetSellerEvents and GetSellerTransactions</Title>
								<URL>http://ebay.custhelp.com/cgi-bin/ebay.cfg/php/enduser/std_adp.php?p_faqid=222</URL>
							</SeeLink>
								<CallInfo>
									<CallName>GetSellerEvents</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerList -->
	<xs:element name="GetSellerListRequest" type="ns:GetSellerListRequestType"/>
	<xs:complexType name="GetSellerListRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns a list of the items posted by the authenticated user, including
				the related item data.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel, GranularityLevel</TempInfo>
				<RelatedCalls>AddItem, GetBidderList, GetItem, RelistItem, ReviseItem</RelatedCalls>
				<SeeLink>
					<Title>GetSellerList</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GetSellerList_BP</URL>
				</SeeLink>
				<SeeLink>
					<Title>Browsing a Seller's Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BrowsingSellerItems</URL>
				</SeeLink>
				<RelatedCalls>
					GetBidderList
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="UserID" type="ns:UserIDType" minOccurs="0" maxOccurs="1">
						<xs:annotation>
							<xs:documentation>
								Specifies the seller whose items will be returned. UserID is an optional
								input. If not specified, retrieves listings for the user identified by the
								authentication token passed in the request. Note that since user
								information is anonymous to everyone except the bidder and the seller
								(during an active auction), only sellers looking for information about
								their own listings and bidders who know the user IDs of their sellers will
								be able to make this API call successfully. See &lt;a href=
								"http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=AnonymousUserInfo"
								&gt;Working with Anonymous User Information&lt;/a&gt;in the eBay Web
								Services Guide for more information.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MotorsDealerUsers" type="ns:UserIDArrayType" minOccurs="0" maxOccurs="1">
						<xs:annotation>
							<xs:documentation>
								Specifies the list of Motors Dealer sellers for which a special set of
								metrics can be requested. Applies to eBay Motors Pro applications only.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the earliest (oldest) date to use in a date range filter based on
								item end time. Specify either an end-time range or a start-time range
								filter in every call request. Each of the time ranges must be a value less than
								120 days.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the latest (most recent) date to use in a date range filter based
								on item end time. Must be specified if EndTimeFrom is specified.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Sort" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the order in which returned items are sorted (based on the end
								dates of the item listings). Valid values:
								&lt;br&gt;
									0 = No sorting&lt;br&gt;
									1 = Sort in descending order&lt;br&gt;
									2 = Sort in ascending order&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the earliest (oldest) date to use in a date range filter based on
								item start time. Each of the time ranges must be a value less than
								120 days. In all calls, at least one date-range filter must be specified
								(i.e., you must specify either the end time range or start time range
								in every request).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the latest (most recent) date to use in a date range filter based
								on item start time. Must be specified if StartTimeFrom is specified.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the data controlling the pagination of the returned values.
								If you set a DetailLevel in this call, you must set pagination values.
								The Pagination field contains
								the number of items to be returned per page of data (per call),
								and the page number to return with the current call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="GranularityLevel" type="ns:GranularityLevelCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the subset of item and user fields to return. See GetSellerList
								in the eBay Web Services guide for a list of the fields that are returned
								for each granularity level. For GetSellerList, use DetailLevel or
								GranularityLevel in a request, but not both. For GetSellerList, if
								GranularityLevel is specified, DetailLevel is ignored.
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>GetSellerList</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GetSellerList_BP</URL>
								</SeeLink>
								<PresentDetails>Yes</PresentDetails>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKUArray" type="ns:SKUArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container for a set of SKUs.
								Filters (reduces) the response to only include active listings
								that the seller listed with any of the specified SKUs.
								If multiple listings include the same SKU, they are
								all returned (assuming they also match the other criteria
								in the GetSellerList request).&lt;br&gt;
								&lt;br&gt;
								SKUArray can be used to retrieve items listed by the user
								identified in AuthToken or in UserID.&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								Listings with matching SKUs are returned regardless of their
								Item.InventoryTrackingMethod settings.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeWatchCount" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether to include WatchCount in Item nodes returned.
								WatchCount is only returned with DetailLevel ReturnAll.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AdminEndedItemsOnly" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether to return only items that were administratively ended
								based on a policy violation.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The category ID for the items retrieved.
								If you specify CategoryID in a GetSellerList call,
								the response contains only items in the category you specify.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeVariations" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the Variations node is returned for all multi-variation
								listings in the response.&lt;br&gt;
								&lt;br&gt;
								Please note that if the seller includes a large number of
								variations in many listings, using this flag may degrade the
								call's performance. Therefore, when you use this flag, you
								may need to reduce the total number of items you're requesting
								at once.
								For example, you may need to use shorter time ranges in the
								EndTime or StartTime filters, fewer entries per page in
								Pagination, and/or SKUArray.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerList -->
	<xs:element name="GetSellerListResponse" type="ns:GetSellerListResponseType"/>
	<xs:complexType name="GetSellerListResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains a list of the items listed by the seller specified as input. The list of
				items is returned in an ItemArrayType object, in which are returned zero, one, or
				multiple ItemType objects. Each ItemType object contains the detail data for one
				item listing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains information regarding the pagination of data (if pagination is
								used), including total number of pages and total number of entries.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMoreItems" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, there are more items yet to be retrieved. Additional
								GetSellerList calls with higher page numbers or more items per page must
								be made to retrieve these items. Not returned if no items match the
								request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemArray" type="ns:ItemArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the list of the seller's items, one ItemType object per item.
								Returns empty if no items are available that match the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemsPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the number of items that are being returned per page of data
								(i.e., per call). Will be the same as the value specified in the
								Pagination.EntriesPerPage input. Only returned if items are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates which page of data was just returned. Will be the same as the
								value specified in the Pagination.PageNumber input. (If the input is
								higher than the total number of pages, the call fails with an error.)
								Only returned if items are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReturnedItemCountActual" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the total number of items returned (i.e., the number of
								ItemType objects in ItemArray).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Seller" type="ns:UserType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the seller whose items are returned. The seller is the eBay
								member whose UserID was passed in the request. If UserID was not
								specified, the seller is the user who made the request (identified by
								eBayAuthToken).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerList</CallName>
									<Details>DetailLevel: none, ItemReturnDescription, ReturnAll</Details>
									<Details>GranularityLevel: Fine</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerPayments -->
	<xs:element name="GetSellerPaymentsRequest" type="ns:GetSellerPaymentsRequestType"/>
	<xs:complexType name="GetSellerPaymentsRequestType">
		<xs:annotation>
			<xs:documentation>
				&lt;b&gt;Half.com only.&lt;/b&gt;&amp;nbsp;Retrieves a summary of pending or paid payments that Half.com created for the
				seller identified by the authentication token in the request. Only retrieves
				payments that occurred within a particular pay period. Each payment is for one
				order line item in one order. An order can contain order line items for
				multiple items from multiple sellers, but this call only retrieves payments that
				are relevant to one seller. The financial value of a payment is typically based on
				an amount that a buyer paid to Half.com for an order line item, with adjustments for
				shipping costs and Half.com's commission. For most sellers, each month contains
				two pay periods: One from the 1st to the 15th of the month, and one from the 16th
				to the last day of the month. Sellers can refer to their account information on
				the Half.com site to determine their pay periods. (You cannot retrieve a seller's
				pay periods by using eBay Web Services.) When a buyer makes a purchase and an
				order is created, Half.com creates a payment for the seller and marks it as
				Pending in the seller's Half.com account. Within a certain number of days after
				the pay period ends, Half.com settles payments for that period and marks each
				completed payment as Paid. See the Half.com Web site online help for more
				information about how payments are managed.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Half.com</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=HalfOverview</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="PaymentStatus" type="ns:RCSPaymentStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Filter to retrieve only items with the specified payment status (Paid or
								Pending). "Pending payments" are payments that Half.com has created but
								that have not yet been sent to the seller's financial institution. Pending
								payments are typically available once a buyer pays for an order. As
								Half.com processes payments by using periodic batch jobs, the
								GetSellerPayments response might not include an order line item's payment for
								up to 20 minutes after the buyer has paid. You can retrieve pending
								payments for the current pay period. Pending payments that have not been
								settled yet can also be retrieved for previous pay periods. "Paid
								payments" are payments that Half.com processed during previous pay
								periods. Paid payments might not appear in the seller's financial
								institution account balance until a certain number of days after the
								current pay period ends (see the Half.com online help for details). You
								can only retrieve paid payments for one previous pay period at a time.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<AllValuesExcept>Canceled</AllValuesExcept>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaymentTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Time range filter that retrieves Half.com payments that were created within
								a single pay period. Sellers can refer to the Half.com site to determine
								their pay periods. PaymentTimeFrom is the earliest (oldest) time and
								PaymentTimeTo is the latest (most recent) time in the range. Half.com pay
								periods start and end at midnight Pacific time, but the time values are
								stored in the database in GMT (not Pacific time). See "Time Values" in the
								eBay Web Services guide for information about converting between GMT and
								Pacific time. &lt;br&gt;
								&lt;br&gt;
								If you specify a PaymentStatus of Pending, add a buffer of one hour (or one
								day) to both ends of the time range to retrieve more data than you need, and
								then filter the results on the client side as needed. If any pending
								payments match the request, the response may include all payments since the
								beginning of the period. &lt;br&gt;
								&lt;br&gt;
								If you specify a PaymentStatus of Paid, the time range must contain one
								full pay period. That is, PaymentTimeFrom must be earlier or equal the
								start time of the pay period, and PaymentTimeTo must be later than or
								equal to the end time of the pay period. Otherwise, no paid payments are
								returned. For example, if the pay period starts on 2005-09-16 and ends on
								2005-09-30, you could specify an earlier PaymentTimeFrom value of
								2005-09-16T00:00:00.000Z and a later PaymentTimeTo value of
								2005-10-01T12:00:00.000Z. &lt;br&gt;
								&lt;br&gt;
								If you specify a time range that covers two pay periods, only the payments
								from the most recent pay period are returned. The earliest time you can
								specify is 18 months ago.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaymentTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Time range filter that retrieves Half.com payments for a single pay
								period. See the description of PaymentTimeTo for details about using this
								time range filter. For paid payments, this value should be equal to or
								later than the end of the last day of the pay period, where the time is
								converted to GMT. For example, if the period ends on 2005-09-30, you could
								specify 2005-10-01T09:00:00.000Z, which is later than the end of the last
								day.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If many payments are available, you may need to call GetSellerPayments
								multiple times to retrieve all the data. Each result set is returned as a
								page of entries. Use this Pagination information to indicate the maximum
								number of entries to retrieve per page (i.e., per call), the page number
								to retrieve, and other data.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerPayments -->
	<xs:element name="GetSellerPaymentsResponse" type="ns:GetSellerPaymentsResponseType"/>
	<xs:complexType name="GetSellerPaymentsResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns a summary of pending or paid payments that Half.com created for the seller
				identified by the authentication token in the request. Only returns payments that
				occurred within a particular pay period. Each payment is for one transaction for
				one item in one order. An order can contain transactions for multiple items from
				multiple sellers, but this call only retrieves payments that are relevant to one
				seller. Payments are only issued for items and transactions that the seller has
				confirmed (see the Half.com online help for details). The financial value of a
				payment is typically based on an amount that a buyer paid to Half.com for a
				transaction, plus the shipping cost the buyer paid to Half.com for the item, minus
				Half.com's commission. For most sellers, each month contains two pay periods: One
				from the 1st to the 15th of the month, and one from the 16th to the last day of
				the month. Payments are submitted to the seller's financial institution a certain
				number of days after the current pay period ends (see the Half.com online help for
				details).
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Contains information regarding the pagination of data (if pagination is used),
							including total number of pages and total number of entries.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMorePayments" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, there are more payments yet to be retrieved. Additional
								GetSellerPayments calls with higher page numbers or more entries per page
								must be made to retrieve these payments. If false, no more payments are
								available or no payments match the request (based on the payment status
								and time filter).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerPayment" type="ns:SellerPaymentType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Information about a single payment that matches the criteria in the
								request. A payment is between Half.com and a seller. Each payment is for
								one transaction for one item in one order. An order can contain
								transactions for multiple items from multiple sellers, but this call only
								retrieves payments that are relevant to one seller. The financial value of
								a payment is typically based on an amount that a buyer paid to Half.com
								for a transaction, plus the shipping cost the buyer paid for the item,
								minus Half.com's commission. Payments can also describe refunds that the
								seller has issued. Multiple SellerPayment entries can be returned per page
								of results. Typically, they are returned in reverse chronological order
								(most recent PaidTime first). Only returned if payments exist that match
								the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaymentsPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the number of payments that can be returned per page of data
								(i.e., per call). This is the same as the value specified in the
								Pagination.EntriesPerPage input (or the default value, if EntriesPerPage
								was not specified). This is not necessarily the actual number of payments
								returned per page (see ReturnedPaymentCountActual).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates which page of data holds the current result set. Will be the
								same as the value specified in the Pagination.PageNumber input. (If the
								input is higher than the total number of pages, the call fails with an
								error.) If no payments are returned, the value is 0. If payments are
								returned, the first page number is 1.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReturnedPaymentCountActual" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the total number of payments returned (i.e., the number of
								SellerPayment entries returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerPayments</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerTransactions -->
	<xs:element name="GetSellerTransactionsRequest" type="ns:GetSellerTransactionsRequestType"/>
	<xs:complexType name="GetSellerTransactionsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves order line item (transaction) information for the user for which the
				call is made, and not for any other user.&amp;nbsp;&lt;b&gt;Also for
				Half.com&lt;/b&gt;. (To retrieve order line items for another seller's listings, use
				GetItemTransactions.)
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Retrieves order line item (transaction) information for the user for which the
					call is made, and not for any other user.&amp;nbsp;&lt;b&gt;Also for
					Half.com&lt;/b&gt;. (To retrieve order line items for another seller's listings, use
					GetItemTransactions.)
				</Summary>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>GetItemTransactions, GetOrderTransactions</RelatedCalls>
				<SeeLink>
					<Title>Email and Address Privacy Policy</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EmailPrivacyPolicy</URL>
					<For>the conditions under which buyer and seller email and address are returned</For>
				</SeeLink>
				<SeeLink>
					<Title>Retrieving Order Line Item Data and Managing Orders</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=RetrievingTransactionsForSpecificSeller</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ModTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ModTimeFrom and ModTimeTo fields specify a date range for retrieving
								order line items associated with the seller. The ModTimeFrom
								field is the starting date range. All of the seller's order line items that were
								last modified within this date range are returned in the output. The
								maximum date range that may be specified is 30 days. This field is not
								applicable if the NumberOfDays date filter is used.
								&lt;br&gt;&lt;br&gt;
								If you don't specify a ModTimeFrom/ModTimeTo filter, the NumberOfDays
								time filter is used and it defaults to 30 (days). 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ModTimeFrom and ModTimeTo fields specify a date range for retrieving
								order line items associated with the seller. The ModTimeTo
								field is the ending date range. All of the seller's order line items that were last
								modified within this date range are returned in the output. The maximum
								date range that may be specified is 30 days. If the ModTimeFrom field is
								used and the ModTimeTo field is omitted, the ModTimeTo value defaults to
								the present time or to 30 days past the ModTimeFrom value (if
								ModTimeFrom value is more than 30 days in the past). This field is not
								applicable if the NumberOfDays date filter is used.
								&lt;br&gt;&lt;br&gt;
								If you don't specify a ModTimeFrom/ModTimeTo filter, the NumberOfDays
								time filter is used and it defaults to 30 (days).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements control pagination of the output. Use EntriesPerPage property to
								control the number of transactions to return per call and PageNumber property to
								specify the page of data to return.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeFinalValueFee" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether to include Final Value Fee (FVF) in the response. For most
								listing types, the Final Value Fee is returned in Transaction.FinalValueFee.
								The Final Value Fee is returned for each order line item.
							&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeContainingOrder" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Include this field and set it to True if you want the ContainingOrder
								container to be returned in the response under each Transaction node.
								For single line item orders, the ContainingOrder.OrderID value takes the
								value of the OrderLineItemID value for the order line item. For Combined
								Payment orders, the ContainingOrder.OrderID value will be shared by at
								least two order line items (transactions) that are part of the same
								order.
							</xs:documentation>
							<xs:appinfo>
							<Default>false</Default>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKUArray" type="ns:SKUArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container for a set of SKUs.
								Filters (reduces) the response to only include order line items
								for listings that include any of the specified SKUs.
								If multiple listings include the same SKU, order line items for
								all of them are returned (assuming they also match the other
								criteria in the GetSellerTransactions request).&lt;br&gt;
								&lt;br&gt;
								You can combine SKUArray with InventoryTrackingMethod.
								For example, if you also pass in InventoryTrackingMethod=SKU,
								the response only includes order line items for listings that
								include InventoryTrackingMethod=SKU and one of the
								requested SKUs.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Platform" type="ns:TransactionPlatformCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Name of the eBay co-branded site upon which the order line item was made.
								This will serve as a filter for the order line items to get emitted in the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NumberOfDays" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								NumberOfDays enables you to specify the number of days' worth of new and modified
								order line items that you want to retrieve. The call response contains the
								order line items whose status was modified within the specified number of days since
								the API call was made. NumberOfDays is often preferable to using the ModTimeFrom
								and ModTimeTo filters because you only need to specify one value. If you use
								NumberOfDays, then ModTimeFrom and ModTimeTo are ignored. For this field, one day
								is defined as 24 hours.
							</xs:documentation>
							<xs:appinfo>
								<Max>30</Max>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="InventoryTrackingMethod" type="ns:InventoryTrackingMethodCodeType" minOccurs="0">
					<xs:annotation>
						<xs:documentation>
								Filters the response to only include order line items for listings
								that match this InventoryTrackingMethod setting. &lt;br&gt;
								&lt;br&gt;
								To track items by seller-defined SKU values instead of by Item IDs, the 
								&lt;b&gt;InventoryTrackingMethod&lt;/b&gt; must be included and set to 'SKU' 
								in the &lt;b&gt;AddFixedPriceItem&lt;/b&gt; (or &lt;b&gt;ReviseFixedPriceItem&lt;/b&gt; 
								or &lt;b&gt;RelistFixedPriceItem&lt;/b&gt;) call.
								&lt;br&gt;
								&lt;br&gt;
								You can combine SKUArray with InventoryTrackingMethod.
								For example, if you set this to SKU and you also pass in
								SKUArray, the response only includes order line items for listings
								that include InventoryTrackingMethod=SKU and one of the
								requested SKUs.
						</xs:documentation>
						<xs:appinfo>
							<CallInfo>
								<CallName>GetSellerTransactions</CallName>
								<RequiredInput>No</RequiredInput>
							</CallInfo>
						</xs:appinfo>
					</xs:annotation>
					</xs:element>
					<xs:element name="IncludeCodiceFiscale" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If this flag is included in the request and set to 'true', the buyer's Codice Fiscale 
								number is returned in the response (if provided by the buyer).
								&lt;br/&gt;&lt;br/&gt;
								This field is only applicable to Italian sellers. The Codice Fiscale number is unique 
								for each Italian citizen and is used for tax purposes.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellerTransactions -->
	<xs:element name="GetSellerTransactionsResponse" type="ns:GetSellerTransactionsResponseType"/>
	<xs:complexType name="GetSellerTransactionsResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns an array of order line item (transaction) data for the seller specified in the request.
				The results can be used to create a report of data that is commonly
				necessary for order processing.
				Zero, one, or many &lt;b&gt;Transaction&lt;/b&gt; objects can be returned in the &lt;b&gt;TransactionArray&lt;/b&gt;.
				The set of order line items returned is limited to those that were modified between
				the times specified in the request's &lt;b&gt;ModTimeFrom&lt;/b&gt; and &lt;b&gt;ModTimeTo&lt;/b&gt; filters.
				The order line items returned are sorted by &lt;b&gt;Transaction.Status.LastTimeModified&lt;/b&gt;,
				ascending order (that is, order line items that more recently were modified are returned last).
				Also returns information about the seller whose order line items were requested.
				If pagination filters were specified in the request, returns meta-data describing
				the effects of those filters on the current response and the estimated effects if
				the same filters are used in subsequent calls.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the total number of order line items that match the input
								criteria and the total number of pages that must be scrolled through to view all order
								line items. To scroll through each page of order line item data, make subsequent 
								&lt;b&gt;GetSellerTransactions&lt;/b&gt; calls, incrementing the &lt;b&gt;Pagination.PageNumber&lt;/b&gt; 
								field by a value of '1' each time.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMoreTransactions" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This flag indicates whether there are additional pages of order line items to view.
								This field will be returned as 'true' if there are additional pages or order line items
								to view, or 'false' if the current page of order line item data is the last page of 
								data.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionsPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This value indicates the number of order line items returned per page (per call) and is
								controlled by the &lt;b&gt;Pagination.EntriesPerPage&lt;/b&gt; value passed in the call
								request. Unless it is the last (or possibly only) page of data (&lt;b&gt;HasMoreTransactions=false&lt;/b&gt;),  
								the &lt;b&gt;TransactionsPerPage&lt;/b&gt; value should equal the 
								&lt;b&gt;Pagination.EntriesPerPage&lt;/b&gt; value passed in the call request.
								&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								Due to the fact that item data on the eBay platform has a shorter retention period than 
								order data, it is possible that some retrieved pages will contain no data. For pages 
								that contain no data, the &lt;b&gt;ReturnedTransactionCountActual&lt;/b&gt; value will 
								be '0'. It is also possible that pages 2, 3, and 4 have no data, but pages 1 and 5 do 
								have data. Therefore, we recommend that you scroll through each page of data (making 
								subsequent &lt;b&gt;GetSellerTransactions&lt;/b&gt; calls and incrementing the
								&lt;b&gt;Pagination.PageNumber&lt;/b&gt; value by '1' each time) until you reach the 
								last page, indicated by &lt;b&gt;HasMoreTransactions=false&lt;/b&gt;.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This value indicates the page number of retrieved order line items that match the input
								criteria. This value is controlled by the &lt;b&gt;Pagination.PageNumber&lt;/b&gt;
								value passed in the call request. To scroll through all pages of order line items that match the 
								input criteria, you increment the &lt;b&gt;Pagination.PageNumber&lt;/b&gt; value by '1' 
								with each subsequent &lt;b&gt;GetSellerTransactions&lt;/b&gt; call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReturnedTransactionCountActual" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This value indicates the total number of (non-empty) order line items retrieved in the
								current page of results. The &lt;b&gt;ReturnedTransactionCountActual&lt;/b&gt; value
								will be lower than the &lt;b&gt;TransactionsPerPage&lt;/b&gt; value if one or more 
								empty order line items are retreived on the page.
								&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								Due to the fact that item data on the eBay platform has a shorter retention period than 
								order data, it is possible that some retrieved pages will contain no data. For pages 
								that contain no order line item data, the &lt;b&gt;ReturnedTransactionCountActual&lt;/b&gt; value will 
								be '0'. It is also possible that pages 2, 3, and 4 have no data, but pages 1 and 5 do 
								have data. Therefore, we recommend that you scroll through each page of data (making 
								subsequent &lt;b&gt;GetSellerTransactions&lt;/b&gt; calls and incrementing the
								&lt;b&gt;Pagination.PageNumber&lt;/b&gt; value by '1' each time) until you reach the 
								last page, indicated by &lt;b&gt;HasMoreTransactions=false&lt;/b&gt;.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Seller" type="ns:UserType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains information about the seller whose order line items are being returned.
								See the reference guide for information about the &lt;b&gt;Seller&lt;/b&gt; object fields
								that are returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionArray" type="ns:TransactionArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								List of &lt;b&gt;Transaction&lt;/b&gt; objects representing the seller's recent sales.
								Each &lt;b&gt;Transaction&lt;/b&gt; object contains the data for one purchase
								(of one or more items in the same listing).
								See the reference guide for more information about the fields that are returned
								for each order line item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PayPalPreferred" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether the seller has the preference enabled that shows that the seller
								prefers PayPal as the method of payment for an item. This preference is indicated on
								an item's View Item page and is intended to influence a buyer to use PayPal
								to pay for the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellerTransactions</CallName>
									<Details>DetailLevel: none, ReturnAll, ItemReturnDescription</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerAlerts -->
	<xs:element name="GetSellingManagerAlertsRequest" type="ns:GetSellingManagerAlertsRequestType"/>
	<xs:complexType name="GetSellingManagerAlertsRequestType">
		<xs:annotation>
			<xs:documentation>
			  Retrieves Selling Manager alerts.
				This call is subject to change without notice; the deprecation process is
				inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerAlerts -->
	<xs:element name="GetSellingManagerAlertsResponse" type="ns:GetSellingManagerAlertsResponseType"/>
	<xs:complexType name="GetSellingManagerAlertsResponseType">
		<xs:annotation>
			<xs:documentation>
				Type defining the call-specific response fields for the &lt;b&gt;GetSellingManagerAlerts&lt;/b&gt; 
				call.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Alert" type="ns:SellingManagerAlertType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Container consisting of details related to a Selling Manager alert. Alert types 
								include listing automation, inventory, PaisaPay (India only), item sold, and 
								a general alert.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
								<CallName>GetSellingManagerAlerts</CallName>
								<Returned>Conditionally</Returned>
							</CallInfo>
						</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerEmailLog -->
	<xs:element name="GetSellingManagerEmailLogRequest" type="ns:GetSellingManagerEmailLogRequestType">
	</xs:element>
	<xs:complexType name="GetSellingManagerEmailLogRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a log of emails sent, or scheduled to be sent, to buyers.
				&lt;br&gt;&lt;br&gt;
				The standard Trading API
				deprecation process is not applicable to this call.
	    </xs:documentation>
			<xs:appinfo>
				<Summary>
					Retrieves a log of emails sent, or scheduled to be sent, to buyers. Includes
					success or failure status.
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for the eBay item listing associated with the Selling
								Manager email log. Unless the &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; value is
								specified in the request, the &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt; fields must be
								used to identify the Selling Manager email log to retrieve. You can
								use &lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; to retrieve the &lt;b&gt;ItemID&lt;/b&gt;, &lt;b&gt;TransactionID&lt;/b&gt;
								or &lt;b&gt;OrderLineItemID&lt;/b&gt; values that correspond to the Selling Manager sale
								record (&lt;b&gt;SaleRecordID&lt;/b&gt;). All four of these fields are returned under the
								&lt;b&gt;SellingManagerSoldTransaction&lt;/b&gt; container of the
								&lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerEmailLog</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for the order line item (transaction) associated with
								the Selling Manager email log. Unless the &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt;
								value is specified in the request, the &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt; fields
								must be used to identify the Selling Manager email log to retrieve.
								You can use &lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; to retrieve the &lt;b&gt;ItemID&lt;/b&gt;,
								&lt;b&gt;TransactionID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; values that correspond to the Selling
								Manager sale record (&lt;b&gt;SaleRecordID&lt;/b&gt;). All four of these fields are
								returned under the &lt;b&gt;SellingManagerSoldTransaction&lt;/b&gt; container of the
								&lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerEmailLog</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderID" type="ns:OrderIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier that identifies a single line item or multiple line item
								(Combined Payment) order associated with the Selling Manager email log. 
								&lt;br&gt;&lt;br&gt;
								For a single line item order, the &lt;b&gt;OrderID&lt;/b&gt; value is identical to the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value that is generated upon creation of the order line
								item. For a Combined Payment order, the &lt;b&gt;OrderID&lt;/b&gt; value is created by eBay
								when the buyer or seller (sharing multiple, common order line items)
								combines multiple order line items into a Combined Payment order through
								the eBay site (or when the seller creates Combined Payment order through
								&lt;b&gt;AddOrder&lt;/b&gt;). If an &lt;b&gt;OrderID&lt;/b&gt; is used in the request, the &lt;b&gt;OrderLineItemID&lt;/b&gt; and
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair are not required.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50</MaxLength>
								<CallInfo>
									<CallName>GetSellingManagerEmailLog</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EmailDateRange" type="ns:TimeRangeType" minOccurs="0">
					  <xs:annotation>
					   <xs:documentation>
               Specifies the earliest (oldest) and latest (most recent) dates to use in a
							 date range filter based on email sent date. Each of the time ranges can be
							 up to 90 days.
              </xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerEmailLog</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
					  </xs:annotation>
					 </xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for an eBay order line item that is associated with
								the Selling Manager email log. This field is created as soon as there
								is a commitment to buy from the seller, and its value is based upon the
								concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a hyphen in between
								these two IDs. You can use &lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; to retrieve the
								&lt;b&gt;ItemID&lt;/b&gt;, &lt;b&gt;TransactionID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; values that correspond to the
								Selling Manager sale record (&lt;b&gt;SaleRecordID&lt;/b&gt;). All four of these fields are
								returned under the &lt;b&gt;SellingManagerSoldTransaction&lt;/b&gt; container of the
								&lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; request. Unless an &lt;b&gt;OrderID&lt;/b&gt; or an
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is specified in the &lt;b&gt;GetSellingManagerSaleRecord&lt;/b&gt;
								request, the &lt;b&gt;OrderLineItemID&lt;/b&gt; is required. 
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50 (Note: ItemIDs and TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>GetSellingManagerEmailLog</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerEmailLog -->
	<xs:element name="GetSellingManagerEmailLogResponse" type="ns:GetSellingManagerEmailLogResponseType"/>
	<xs:complexType name="GetSellingManagerEmailLogResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the log of emails not sent.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="EmailLog" type="ns:SellingManagerEmailLogType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Email logs associated with this order.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerEmailLog</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerInventory -->
	<xs:element name="GetSellingManagerInventoryRequest" type="ns:GetSellingManagerInventoryRequestType">
	</xs:element>
	<xs:complexType name="GetSellingManagerInventoryRequestType">
		<xs:annotation>
			<xs:documentation>
	      Retrieves a paginated list containing details of a user's Selling Manager inventory.
				This call is subject to change without notice; the deprecation process is
				inapplicable to this call.
	    </xs:documentation>
			<xs:appinfo>
				<Summary>
					Retrieves a paginated listing of a user's Selling Manager inventory.
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Sort" type="ns:SellingManagerProductSortCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Sets the sorting method for the results.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the inventory folder containing the requested inventory information.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Details about how many Products to return per page and which page to view.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SortOrder" type="ns:SortOrderCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Order to be used for sorting retrieved product lists.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Search" type="ns:SellingManagerSearchType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Specifies types and values to search for in the seller's listings.
 							</xs:documentation>
 							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StoreCategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Specifies a store category whose products will be returned.
 							</xs:documentation>
 							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Filter" type="ns:SellingManagerInventoryPropertyTypeCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
							  Container for the list of filters that can be applied to the inventory information requested.
 							</xs:documentation>
 							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerInventory -->
	<xs:element name="GetSellingManagerInventoryResponse" type="ns:GetSellingManagerInventoryResponseType"/>
	<xs:complexType name="GetSellingManagerInventoryResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains a list of the products created by the seller. The list of products is returned as a set
				of tags, in which are returned zero, one, or multiple SellingManagerProductType objects. Each
				SellingManagerProductType object contains the information about for one Selling Manager product
				and any Selling Manager templates the product contains.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="InventoryCountLastCalculatedDate" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns the date the inventory counts were last calculated.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
								<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingManagerProduct" type="ns:SellingManagerProductType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Container for information about the requested products and templates.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Contains the total number of pages (TotalNumberOfPages) and the total
							number of products entries (TotalNumberOfEntries) that can be returned
							on repeated calls with the same format and report criteria.
						</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventory</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerInventoryFolder -->
	<xs:element name="GetSellingManagerInventoryFolderRequest" type="ns:GetSellingManagerInventoryFolderRequestType"/>
	<xs:complexType name="GetSellingManagerInventoryFolderRequestType">
		<xs:annotation>
			<xs:documentation>
			  Retrieves Selling Manager inventory folders.
				This call is subject to change without notice; the deprecation process is
				inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="FolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  If a FolderID is submitted, all child-folders below this folder will be returned.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventoryFolder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MaxDepth" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the number of levels of subfolders to be returned. If 0, the parent folder
								is returned. If 1, the parent and child folders are returned. If 2, the parent and
								two levels of child folders are returned. Ignored if FullRecursion is set to True.
 							</xs:documentation>
							<xs:appinfo>
								<Default>1</Default>
								<CallInfo>
									<CallName>GetSellingManagerInventoryFolder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FullRecursion" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Displays the entire tree of a user's folders. If this is provided, FolderID and MaxDepth
								need not be given.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventoryFolder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerInventoryFolder -->
	<xs:element name="GetSellingManagerInventoryFolderResponse" type="ns:GetSellingManagerInventoryFolderResponseType"/>
	<xs:complexType name="GetSellingManagerInventoryFolderResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the folder structure of the input folderID.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Folder" type="ns:SellingManagerFolderDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Details of the requested folder.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerInventoryFolder</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerItemAutomationRule -->
	<xs:element name="GetSellingManagerItemAutomationRuleRequest" type="ns:GetSellingManagerItemAutomationRuleRequestType">
	</xs:element>
	<xs:complexType name="GetSellingManagerItemAutomationRuleRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the set of Selling Manager automation rules
				associated with an item.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
				<RelatedCalls>SetSellingManagerItemAutomationRule</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the item whose Selling Manager automation rules
								you want to retrieve.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerItemAutomationRule</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerItemAutomationRule -->
	<xs:element name="GetSellingManagerItemAutomationRuleResponse" type="ns:GetSellingManagerItemAutomationRuleResponseType"/>
	<xs:complexType name="GetSellingManagerItemAutomationRuleResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the set of automation rules associated with the specified item.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AutomatedListingRule" type="ns:SellingManagerAutoListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated listing rule associated with the item.
								This field is only returned if the item was listed from a template. 
								The value in this field refers to that template's automated listing rule.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedRelistingRule" type="ns:SellingManagerAutoRelistType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated relisting rule associated with the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedSecondChanceOfferRule" type="ns:SellingManagerAutoSecondChanceOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated second chance offer rule associated with the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains fees that may be incurred when items are listed using the 
								automation rule (e.g., a scheduled listing fee). Use of an automation rule 
								does not in itself have a fee, but use can result in a fee.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerSaleRecord -->
	<xs:element name="GetSellingManagerSaleRecordRequest" type="ns:GetSellingManagerSaleRecordRequestType"/>
	<xs:complexType name="GetSellingManagerSaleRecordRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the data for one or more Selling Manager sale records. 
				&lt;br&gt;&lt;br&gt;
				The standard Trading API
				deprecation process is not applicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for the eBay item listing associated with the Selling
								Manager sale record. Unless the &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; value is
								specified in the request, the &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt; fields must be
								used to identify the Selling Manager sale record to retrieve. You can
								use &lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; to retrieve the &lt;b&gt;ItemID&lt;/b&gt;, &lt;b&gt;TransactionID&lt;/b&gt;
								or &lt;b&gt;OrderLineItemID&lt;/b&gt; values that correspond to the Selling Manager sale
								record (&lt;b&gt;SaleRecordID&lt;/b&gt;). All four of these fields are returned under the
								&lt;b&gt;SellingManagerSoldTransaction&lt;/b&gt; container of the
								&lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for the order line item (transaction) associated with
								the Selling Manager sale record. Unless the &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt;
								value is specified in the request, the &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt; fields
								must be used to identify the Selling Manager sale record to retrieve.
								You can use &lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; to retrieve the &lt;b&gt;ItemID&lt;/b&gt;,
								&lt;b&gt;TransactionID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; values that correspond to the Selling
								Manager sale record (&lt;b&gt;SaleRecordID&lt;/b&gt;). All four of these fields are
								returned under the &lt;b&gt;SellingManagerSoldTransaction&lt;/b&gt; container of the
								&lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderID" type="ns:OrderIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier that identifies a single line item or multiple line item
								(Combined Payment) order associated with the Selling Manager sale record(s). 
								&lt;br&gt;&lt;br&gt;
								For a single line item order, the &lt;b&gt;OrderID&lt;/b&gt; value is identical to the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value that is generated upon creation of the order line
								item. For a Combined Payment order, the &lt;b&gt;OrderID&lt;/b&gt;value is created by eBay
								when the buyer or seller (sharing multiple, common order line items)
								combines multiple order line items into a Combined Payment order through
								the eBay site (or when the seller creates Combined Payment order through
								&lt;b&gt;AddOrder&lt;/b&gt;). If an &lt;b&gt;OrderID&lt;/b&gt; is used in the request, the &lt;b&gt;OrderLineItemID&lt;/b&gt; and
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair are not required.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for an eBay order line item that is associated with
								the Selling Manager sale record. This field is created as soon as there
								is a commitment to buy from the seller, and its value is based upon the
								concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a hyphen in between
								these two IDs. You can use &lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; to retrieve the
								&lt;b&gt;ItemID&lt;/b&gt;, &lt;b&gt;TransactionID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; values that correspond to the
								Selling Manager sale record (&lt;b&gt;SaleRecordID&lt;/b&gt;). All four of these fields are
								returned under the &lt;b&gt;SellingManagerSoldTransaction&lt;/b&gt; container of the
								&lt;b&gt;GetSellingManagerSoldListings&lt;/b&gt; request. Unless an &lt;b&gt;OrderID&lt;/b&gt; or an
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;Transaction&lt;/b&gt; pair is specified in the &lt;b&gt;GetSellingManagerSaleRecord&lt;/b&gt;
								request, the &lt;b&gt;OrderLineItemID&lt;/b&gt; is required. 
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50 (Note: ItemIDs and TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>GetSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerSaleRecord -->
	<xs:element name="GetSellingManagerSaleRecordResponse" type="ns:GetSellingManagerSaleRecordResponseType"/>
	<xs:complexType name="GetSellingManagerSaleRecordResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to a GetSellingManagerSaleRecord call.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SellingManagerSoldOrder" type="ns:SellingManagerSoldOrderType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the data in a Selling Manager sale record.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSaleRecord</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerSoldListings -->
	<xs:element name="GetSellingManagerSoldListingsRequest" type="ns:GetSellingManagerSoldListingsRequestType"/>
	<xs:complexType name="GetSellingManagerSoldListingsRequestType">
		<xs:annotation>
			<xs:documentation>
			  Returns a Selling Manager user's sold listings.
				&lt;br&gt;&lt;br&gt;
				This call is subject to change without notice; the deprecation process is
				inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Retrieves information about items that a seller has sold.
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Search" type="ns:SellingManagerSearchType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Search filters for sold listings.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StoreCategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Listings with this store category ID will be listed.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Filter" type="ns:SellingManagerSoldListingsPropertyTypeCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
							  This holds the list of filters that can be applicable for sold listings.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Archived" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Requests listing records that are more than 90 days old. Records are archived between 90
							and 120 days after being created, and thereafter can only be retrieved using this tag.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Sort" type="ns:SellingManagerSoldListingsSortTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Field to be used to sort the response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SortOrder" type="ns:SortOrderCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Order to be used for sorting the requested listings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Details about how many listings to return per page and which page to view.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SaleDateRange" type="ns:TimeRangeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Specifies the earliest (oldest) and latest (most recent) dates to use in a date
								range filter based on item start time. A time range can be up to 120
								days.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerSoldListings -->
	<xs:element name="GetSellingManagerSoldListingsResponse" type="ns:GetSellingManagerSoldListingsResponseType"/>
	<xs:complexType name="GetSellingManagerSoldListingsResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns a Selling Manager user's sold listings. Response can be filtered by date, search
				values, and stores.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SaleRecord" type="ns:SellingManagerSoldOrderType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Returns a Selling Manager user's sold listings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the total number of pages (TotalNumberOfPages) and the total
								number of products entries (TotalNumberOfEntries) that can be returned
								on repeated calls with the same format and report criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerSoldListings</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerTemplateAutomationRule -->
	<xs:element name="GetSellingManagerTemplateAutomationRuleRequest" type="ns:GetSellingManagerTemplateAutomationRuleRequestType">
	</xs:element>
	<xs:complexType name="GetSellingManagerTemplateAutomationRuleRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the set of Selling Manager automation rules associated
				with a Selling Manager template.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates,SetSellingManagerTemplateAutomationRule</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
				<RelatedCalls>SetSellingManagerTemplateAutomationRule</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the Selling Manager template whose Selling Manager
								automation rules you want to retrieve.
								You can obtain a SaleTemplateID by calling GetSellingManagerInventory.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerTemplateAutomationRule -->
	<xs:element name="GetSellingManagerTemplateAutomationRuleResponse" type="ns:GetSellingManagerTemplateAutomationRuleResponseType"/>
	<xs:complexType name="GetSellingManagerTemplateAutomationRuleResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the set of automation rules associated with the specified template.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AutomatedListingRule" type="ns:SellingManagerAutoListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated listing rule associated with the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedRelistingRule" type="ns:SellingManagerAutoRelistType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated relisting rule associated with the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedSecondChanceOfferRule" type="ns:SellingManagerAutoSecondChanceOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated second chance offer rule associated with the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains fees that may be incurred when items are listed using the 
								automation rule (e.g., a scheduled listing fee). Use of an automation rule 
								does not in itself have a fee, but use can result in a fee.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerTemplates -->
	<xs:element name="GetSellingManagerTemplatesRequest" type="ns:GetSellingManagerTemplatesRequestType"/>
	<xs:complexType name="GetSellingManagerTemplatesRequestType">
		<xs:annotation>
			<xs:documentation>
	 			Retrieves Selling Manager templates.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The ID of the template whose data will be returned.
								A SaleTemplateID is the ID of a Selling Manager template.
								A Selling Manager template contains the data needed to list an item.
								One or more template IDs can be specified, each in
								its own container.
								You can obtain a SaleTemplateID by calling GetSellingManagerInventory.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerTemplates</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSellingManagerTemplates -->
	<xs:element name="GetSellingManagerTemplatesResponse" type="ns:GetSellingManagerTemplatesResponseType"/>
	<xs:complexType name="GetSellingManagerTemplatesResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the templates requested on input. 
				Each SellingManagerTemplateType object in the response contains the data for one
				Selling Manager template.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SellingManagerTemplateDetailsArray" type="ns:SellingManagerTemplateDetailsArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the data of the templates requested on input. 
								A Selling Manager template contains the data needed to list an item.
								Empty if no items are available that match the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSellingManagerTemplates</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSessionID -->
	<xs:element name="GetSessionIDRequest" type="ns:GetSessionIDRequestType"/>
	<xs:complexType name="GetSessionIDRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a session ID that identifies a user and your application when you make a
				FetchToken request.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>ConfirmIdentity, FetchToken, GetTokenStatus, RevokeToken</RelatedCalls>
				<SeeLink>
					<Title>Getting Tokens</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingAToken</URL>
				</SeeLink>
				<SeeLink>
					<Title>Getting Tokens for Applications with Multiple Users</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingATokenViaFetchToken</URL>
				</SeeLink>
				<SeeLink>
					<Title>Setting Up an Application to Receive Tokens</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=RuName</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="RuName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The runame provided must match the one that will be used for validation
								during the creation of a user token.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSessionID</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSessionID -->
	<xs:element name="GetSessionIDResponse" type="ns:GetSessionIDResponseType"/>
	<xs:complexType name="GetSessionIDResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the generated SessionID, which is a unique identifier for authenticating data entry during the process that creates a user token.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SessionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A 40-character identifier supplied by eBay to an application. Used to confirm the
								identities of the user and the application in a URL redirect during the
								process in which the user agrees to let the application wield a user token that
								grants the application the right to access eBay data on behalf of the user.
								Subsequently also used as input for the FetchToken API call. The
								SessionID is valid for five minutes after it is retrieved.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSessionID</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetShippingDiscountProfiles -->
	<xs:element name="GetShippingDiscountProfilesRequest" type="ns:GetShippingDiscountProfilesRequestType"/>
	<xs:complexType name="GetShippingDiscountProfilesRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns the shipping discount profiles defined by the user, along with other combined
				payment-related details such as packaging and handling costs.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddItem, GetItem, RelistItem, RevisteItem, SetShippingDiscountProfiles, VerifyAddItem
				</RelatedCalls>
				<SeeLink>
					<Title>Other Shipping Features</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ShippingDiscountProfiles</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType" />
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetShippingDiscountProfiles -->
	<xs:element name="GetShippingDiscountProfilesResponse" type="ns:GetShippingDiscountProfilesResponseType"/>
	<xs:complexType name="GetShippingDiscountProfilesResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to call of GetShippingDiscountProfiles.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CurrencyID" type="ns:CurrencyCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The three-digit code of the currency to be used for shipping cost discounts and
								insurance for combined payment orders. A discount profile can only be associated
								with a listing if the &lt;b&gt;CurrencyID&lt;/b&gt; value of the profile matches the 
								&lt;b&gt;Item.Currency&lt;/b&gt; value specified in a listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FlatShippingDiscount" type="ns:FlatShippingDiscountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Details of an individual discount profile defined by the
								user for flat rate shipping--one for each profile defined by the user.
								Empty if no shipping discount profiles were defined.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CalculatedShippingDiscount" type="ns:CalculatedShippingDiscountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Details of an individual discount profile defined by the
								user for calculated shipping--one for each profile defined by the user.
								Empty if no shipping discount profiles were defined.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionalShippingDiscount" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether the user defined a promotional discount (the discount is active
								as soon as it exists).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CalculatedHandlingDiscount" type="ns:CalculatedHandlingDiscountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container is used by the seller to specify/modify packaging and handling discounts that are applied 
								for combined payment orders. This container is only returned if it is set for the Shipping Discount Profile.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionalShippingDiscountDetails" type="ns:PromotionalShippingDiscountDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The data for the specific promotional shipping discount.
								Returned only if it has been defined.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingInsurance" type="ns:ShippingInsuranceType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The data for the domestic insurance for combined payment.
								Returned only if it has been defined.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="InternationalShippingInsurance" type="ns:ShippingInsuranceType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The data for the international insurance for combined payment.
								Returned only if it has been defined.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CombinedDuration" type="ns:CombinedPaymentPeriodCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field indicates the number of days after the sale of an
								item in which the buyer or seller can combine multiple and mutual order
								line items into one Combined Payment order. In a Combined Payment order,
								the buyer makes one payment for all order line items, hence only unpaid
								order line items can be combined into a Combined Payment order.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetShippingDiscountProfiles</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStore -->
	<xs:element name="GetStoreRequest" type="ns:GetStoreRequestType"/>
	<xs:complexType name="GetStoreRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves configuration information for the eBay store owned by the specified
				UserID, or by the caller.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					GetStoreCategoryUpdateStatus, GetStoreCustomPage, GetStoreOptions,
					SetStore, SetStoreCategories, SetStoreCustomPage
				</RelatedCalls>
				<SeeLink>
					<Title>Managing eBay Stores</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingeBayStores</URL>
				</SeeLink>
				<SeeLink>
					<Title>Editing the Store Settings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EditingStoreSettings</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CategoryStructureOnly" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								 If this is set to True, only the category structure of the store is
								 returned. If this is not specified or set to False, the complete store
								 configuration is returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStore</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RootCategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the category ID for the topmost category to return (along with
								the subcategories under it, the value of the LevelLimit property
								determining how deep). This tag is optional. If RootCategoryID is not
								specified, then the category tree starting at that root Category is
								returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStore</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LevelLimit" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								 Specifies the limit for the number of levels of the category hierarchy
								 to return, where the given root category is level 1 and its children are
								 level 2. Only categories at or above the level specified are returned.
								 This tag is optional. If LevelLimit is not set, the complete category
								 hierarchy is returned. Stores support category hierarchies up to 3
								 levels only.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStore</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the user whose store data is to be returned. If not specified,
								then the store returned is that for the requesting user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStore</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStore -->
	<xs:element name="GetStoreResponse" type="ns:GetStoreResponseType"/>
	<xs:complexType name="GetStoreResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the data describing a seller's eBay store, including name, description,
				URL, and other information. The caller making the request must be the owner
				of an eBay store. If the authenticated caller does not have an eBay store, the
				response is an error. A successful response contains either the complete store
				configuration or information about the category hierarchy for the store only.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Store" type="ns:StoreType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The data describing the store configuration.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStore</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStoreCategoryUpdateStatus -->
	<xs:element name="GetStoreCategoryUpdateStatusRequest" type="ns:GetStoreCategoryUpdateStatusRequestType"/>
	<xs:complexType name="GetStoreCategoryUpdateStatusRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of the processing for category-structure changes specified
				with a call to SetStoreCategories.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetStore, SetStore, SetStoreCategories</RelatedCalls>
				<SeeLink>
					<Title>Managing eBay Stores</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingeBayStores</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="TaskID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The task ID returned by the SetStoreCategories call. If the
								SetStoreCategories call was processed asynchronously, the TaskID will be
								a positive number. If SetStoreCategories returned a TaskID with a value of
								0, the change was completed at the time the call was made (and there is
								no need to check status).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreCategoryUpdateStatus</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStoreCategoryUpdateStatus -->
	<xs:element name="GetStoreCategoryUpdateStatusResponse" type="ns:GetStoreCategoryUpdateStatusResponseType"/>
	<xs:complexType name="GetStoreCategoryUpdateStatusResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the store category structure update status, when a prior 
				SetStoreCategories call was processed asynchronously. If a SetStoreCategories 
				request affects many listings, then the category structure changes will be 
				processed asynchronously. If not many listings are affected by category structure 
				changes, the status is returned in the SetStoreCategories response.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Status" type="ns:TaskStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The status (Pending, InProgress, Complete, or Failed) of an update to the 
								store category structure. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreCategoryUpdateStatus</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStoreCustomPage -->
	<xs:element name="GetStoreCustomPageRequest" type="ns:GetStoreCustomPageRequestType"/>
	<xs:complexType name="GetStoreCustomPageRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the custom page or pages for the authenticated user's Store.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetStoreOptions, GetStore, SetStore, SetStoreCustomPage</RelatedCalls>
				<SeeLink>
					<Title>Managing Custom Pages</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingCustomPages</URL>
				</SeeLink>
				<SeeLink>
					<Title>Managing eBay Stores</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingeBayStores</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="PageID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If a PageID is specified, then that page is returned, and the returned page
								contains the page Content. If no PageID is specified, then all pages are
								returned, without the page Content.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreCustomPage</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStoreCustomPage -->
	<xs:element name="GetStoreCustomPageResponse" type="ns:GetStoreCustomPageResponseType"/>
	<xs:complexType name="GetStoreCustomPageResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the custom page or pages for the user's Store.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CustomPageArray" type="ns:StoreCustomPageArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The custom page or custom pages.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreCustomPage</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStoreOptions -->
	<xs:element name="GetStoreOptionsRequest" type="ns:GetStoreOptionsRequestType"/>
	<xs:complexType name="GetStoreOptionsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the current list of eBay store configuration settings.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetStore</RelatedCalls>
				<SeeLink>
					<Title>Editing the Store Settings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EditingStoreSettings</URL>
				</SeeLink>
				<SeeLink>
					<Title>Managing eBay Stores</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingeBayStores</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStoreOptions -->
	<xs:element name="GetStoreOptionsResponse" type="ns:GetStoreOptionsResponseType"/>
	<xs:complexType name="GetStoreOptionsResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the current list of options for Store configurations.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="BasicThemeArray" type="ns:StoreThemeArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The current set of basic themes. Each basic theme definition
								specifies a valid color scheme for the theme.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreOptions</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AdvancedThemeArray" type="ns:StoreThemeArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The current set of advances themes. Unlike basic themes, you
								can use any color	scheme with an advanced theme. These themes 
								are suitable for more advanced customization.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreOptions</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="LogoArray" type="ns:StoreLogoArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The current set of Store logos. These logos are used in the Store header.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreOptions</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SubscriptionArray" type="ns:StoreSubscriptionArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The current set of eBay Store subscription tiers and corresponding 
								subscription prices.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreOptions</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MaxCategories" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The maximum number of categories in this store.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreOptions</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MaxCategoryLevels" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The maximum number of category levels in this store.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStoreOptions</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStorePreferences -->
	<xs:element name="GetStorePreferencesRequest" type="ns:GetStorePreferencesRequestType"/>
	<xs:complexType name="GetStorePreferencesRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a user's Store preferences.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>SetStore, SetStorePreferences</RelatedCalls>
				<SeeLink>
					<Title>Managing eBay Stores</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingeBayStores</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetStorePreferences -->
	<xs:element name="GetStorePreferencesResponse" type="ns:GetStorePreferencesResponseType"/>
	<xs:complexType name="GetStorePreferencesResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the Store preferences retrieved for a user.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="StorePreferences" type="ns:StorePreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The user's Store preferences.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetStorePreferences</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSuggestedCategories -->
	<xs:element name="GetSuggestedCategoriesRequest" type="ns:GetSuggestedCategoriesRequestType"/>
	<xs:complexType name="GetSuggestedCategoriesRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns a list of up to 10 categories that have the highest percentage of listings
				whose titles or descriptions contain the keywords you specify.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddItem, GetCategories, GetCategoryMappings, GetItemRecommendations
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Query" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the search string, consisting of one or
								more words to search for in the listing title.
								The words "and" and "or" are treated like any other
								word.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>350 (characters)</MaxLength>
								<CallInfo>
									<CallName>GetSuggestedCategories</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetSuggestedCategories -->
	<xs:element name="GetSuggestedCategoriesResponse" type="ns:GetSuggestedCategoriesResponseType"/>
	<xs:complexType name="GetSuggestedCategoriesResponseType">
	  <xs:annotation>
	    <xs:documentation>
				Returns a list of categories with the highest number
				of listings whose titles or descriptions contain the keywords
				specified in a GetSuggestedCategoriesRequest.
	    </xs:documentation>
	  </xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SuggestedCategoryArray" type="ns:SuggestedCategoryArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Contains the categories that contain listings
							that match the query string in the request. The array
							can have up to 10 categories. Not returned if no categories match
							the query in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSuggestedCategories</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
					  </xs:annotation>
					</xs:element>
					<xs:element name="CategoryCount" type="xs:int" minOccurs="0">
					  <xs:annotation>
					    <xs:documentation>
								Indicates the number of categories in the array.
					    </xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetSuggestedCategories</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
					  </xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetTaxTable -->
	<xs:element name="GetTaxTableRequest" type="ns:GetTaxTableRequestType"/>
	<xs:complexType name="GetTaxTableRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the tax table for a user on a given site or retrieves the valid
				jurisdictions (if any) for a given site.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>SetTaxTable</RelatedCalls>
				<TempInfo>DetailLevel</TempInfo>
				<SeeLink>
					<Title>Enabling Multi-jurisdiction Sales Tax</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SalesTax</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetTaxTable -->
	<xs:element name="GetTaxTableResponse" type="ns:GetTaxTableResponseType"/>
	<xs:complexType name="GetTaxTableResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to GetTaxTableRequest.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="LastUpdateTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The last time (in GMT) that the tax table was updated.
								Only returned if the user previously created a tax table
								and if the site has jurisdictions.
								LastUpdateTime is useful for synchronization. If you cache the user's
								tax table, you can use GetTaxTable to check if it has changed and
								whether you need to update the cached tax table.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetTaxTable</CallName>
									<Details>DetailLevel: ReturnAll, none</Details>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TaxTable" type="ns:TaxTableType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A container of tax jurisdiction information unique to
								a user/site combination. Empty if not set for user.
								If DetailLevel is not specified, information is only
								returned for the jurisdictions for which the user provided tax
								information. If DetailLevel is ReturnAll, tax information
								is returned for all possible jurisdictions, whether
								specified by the user or not. ShippingIncludedInTax and
								SalesTaxPercent are returned but are empty.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetTaxTable</CallName>
									<Details>DetailLevel: ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetTokenStatus -->
	<xs:element name="GetTokenStatusRequest" type="ns:GetTokenStatusRequestType"/>
	<xs:complexType name="GetTokenStatusRequestType">
		<xs:annotation>
			<xs:documentation>
				Requests current status of user token.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>FetchToken, RevokeToken</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetTokenStatus -->
	<xs:element name="GetTokenStatusResponse"  type="ns:GetTokenStatusResponseType"/>
	<xs:complexType name="GetTokenStatusResponseType">
		<xs:annotation>
			<xs:documentation>
			Returns token status.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="TokenStatus" type="ns:TokenStatusType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Returns token status and details. For example, if revoked, whether by eBay, the user, or the application, and also when revoked.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetTokenStatus</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetUser -->
	<xs:element name="GetUserRequest" type="ns:GetUserRequestType"/>
	<xs:complexType name="GetUserRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves data pertaining to a single eBay user. Callers can use this call to
				return their own user data or the data of another eBay user. Unless the caller
				passes in an ItemID that identifies a current or past common order, not all
				data (like email addresses) will be returned in the User object.
			</xs:documentation>
			<xs:appinfo>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>
					GetAccount, GetFeedback, GetSellerDashboard,GetSellerEvents,
					GetSellerList, GetSellerTransactions, GetUserPreferences
				</RelatedCalls>
				<SeeLink>
					<Title>Managing User Information</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingUserInformationChapter</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specify the item ID for a successfully concluded listing in which the
								requestor and target user were participants (one as seller and the other
								as buyer). Necessary to return certain data (like an email address). Not
								necessary if the requestor is retrieving their own data. ItemID is an
								optional input.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetUser</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specify the user whose data you want returned by the call. UserID is
								optional. If not specified, eBay returns data pertaining to the
								requesting user (as specified with the eBayAuthToken).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUser</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeExpressRequirements" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field is deprecated.
							</xs:documentation>
							<xs:appinfo>
								<DeprecationVersion>579</DeprecationVersion>
								<DeprecationDetails>NoOp</DeprecationDetails>
								<UseInstead/>
								<Default>false</Default>
								<CallInfo>
									<NoCalls/>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeFeatureEligibility" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If IncludeFeatureEligibility is true, the response includes a
								FeatureEligibility node. (The FeatureEligibility node indicates whether
								the seller can list with certain features.)
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUser</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetUser -->
	<xs:element name="GetUserResponse" type="ns:GetUserResponseType"/>
	<xs:complexType name="GetUserResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the data retrieved by the call. User data is returned in a User object.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="User" type="ns:UserType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the returned user data for the specified eBay user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUser</CallName>
									<Details>DetailLevel: none, ReturnSummary, ReturnAll</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>					
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetUserContactDetails -->
	<xs:element name="GetUserContactDetailsRequest" type="ns:GetUserContactDetailsRequestType"/>
	<xs:complexType name="GetUserContactDetailsRequestType">
		<xs:annotation>
			<xs:documentation>
				Returns contact information for a specified user, given that a bidding relationship
				(as either a buyer or seller) exists between the caller and the user.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddMemberMessagesAAQToBidder, DeleteMyMessages, GetMemberMessages,
					ReviseMyMessages, ReviseMyMessagesFolders
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An eBay item ID that uniquely identifies a currently active item.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetUserContactDetails</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ContactID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An eBay ID that uniquely identifies a given user for whom the caller is seeking
								information. This is the user's eBay username. Either a seller's or bidder's
								username can be specified here, as long as a bidding relationship exists between
								the requester and the user specified by this field. That is, a bidder must be
								bidding on the seller's active item, or have made an offer on the item via Best
								Offer.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserContactDetails</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RequesterID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An eBay ID that uniquely identifies the person who is making the call. This is the
								requester's eBay username. Either a seller's or bidder's username can be specified
								here, as long as a bidding relationship exists between the requester and the
								user for whom information is being requested.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserContactDetails</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetUserContactDetails -->
	<xs:element name="GetUserContactDetailsResponse" type="ns:GetUserContactDetailsResponseType"/>
	<xs:complexType name="GetUserContactDetailsResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns contact information to a seller for both bidders
				and users who have made offers (via Best Offer) during
				an active listing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="UserID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An eBay ID that uniquely identifies a given
								user. The eBay username of the requested
								contact.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserContactDetails</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ContactAddress" type="ns:AddressType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contact information for the requested contact.
								Note that the email address is NOT returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserContactDetails</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RegistrationDate" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The date and time that the requested contact
								registered with eBay.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserContactDetails</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetUserDisputes -->
	<xs:element name="GetUserDisputesRequest" type="ns:GetUserDisputesRequestType"/>
	<xs:complexType name="GetUserDisputesRequestType">
		<xs:annotation>
			<xs:documentation>
				Requests a list of disputes the requester is involved in as buyer or seller.
				eBay Buyer Protection Item Not Received and Significantly Not As Described cases
				are not returned with this call. To retrieve eBay Buyer Protection cases, the
				getUserCases call of the Resolution Case Management API must be used instead.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Requests a list of disputes the requester is involved in as buyer or seller.
					eBay Buyer Protection Item Not Received and Significantly Not As Described cases
					are not returned with this call.
				</Summary>
				<TempInfo>DetailLevel</TempInfo>
				<RelatedCalls>AddDispute, AddDisputeResponse, GetDispute, SellerReverseDispute</RelatedCalls>
				<SeeLink>
					<Title>Unpaid Item Disputes</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UnpaidItemDisputes</URL>
				</SeeLink>
				<SeeLink>
					<Title>Buyer Disputes</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BuyerDisputes</URL>
				</SeeLink>
				<SeeLink>
					<Title>Getting Details About a Dispute</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=GettingDetailsAboutADispute</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="DisputeFilterType" type="ns:DisputeFilterTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An inclusive filter that isolates the returned disputes to a certain
								type such as Item Not Received or Unpaid Item disputes. eBay Buyer
								Protection cases are not retrieved with this call, even if the
								ItemNotReceivedDisputes filter is included in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DisputeSortType" type="ns:DisputeSortTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The value and sequence to use to sort the returned disputes.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							A filter that retrieves disputes whose DisputeModifiedTime is later
							than or equal to this value. Specify the time value in GMT.
							See the eBay Web Services documentation for information about specifying time values.
							For more precise control of the date range filter, it is a good practice to also
							specify ModTimeTo. Otherwise, the end of the date range is the present time.
							Filtering by date range is optional. You can use date range filters in combination
							with other filters like DisputeFilterType to control the amount of data returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModTimeTo" type="xs:dateTime" minOccurs="0">
					<xs:annotation>
						<xs:documentation>
							A filter that retrieves disputes whose DisputeModifiedTime is earlier
							than or equal to this value. Specify the time value in GMT.
							See the eBay Web Services documentation for information about specifying time values.
							For more precise control of the date range filter, it is a good practice to also
							specify ModTimeFrom. Otherwise, all available disputes modified prior to the ModTimeTo value are returned.
							Filtering by date range is optional. You can use date range filters in combination
							with other filters like DisputeFilterType to control the amount of data returned.
						</xs:documentation>
						<xs:appinfo>
							<CallInfo>
								<CallName>GetUserDisputes</CallName>
								<RequiredInput>No</RequiredInput>
							</CallInfo>
						</xs:appinfo>
					</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The virtual page number of the result set to display. A result set has a number of disputes
								divided into virtual pages, with 200 disputes per page. The response can only display one page.
								The first page in the result set is number 1. Required. If not specified, a warning is returned
								and Pagination.PageNumber is set to 1 by default.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetUserDisputes -->
	<xs:element name="GetUserDisputesResponse" type="ns:GetUserDisputesResponseType"/>
	<xs:complexType name="GetUserDisputesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns a list of disputes that involve the calling user
				as buyer or seller, in response to a GetUserDisputesRequest.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="StartingDisputeID" type="ns:DisputeIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The index of the first dispute in the current result set, relative
								to the total number of disputes available.
								Primarily useful for interpreting paginated results.
								For example, if 228 disputes are available and
								200 results are returned per page: The first page returns
								a StartingDisputeID value of 1 and the second page returns a
								StartingDisputeID value of 201.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<Details>DetailLevel: ReturnSummary, ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndingDisputeID" type="ns:DisputeIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The index of the last dispute in the current result set, relative
								to the total number of disputes available.
								Primarily useful for interpreting paginated results.
								For example, if 228 disputes are available and
								200 results are returned per page: The first page returns
								an EndingDisputeID value of 200 and the second page returns an
								EndingDisputeID value of 228.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<Details>DetailLevel: ReturnSummary, ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DisputeArray" type="ns:DisputeArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The array of disputes returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<Details>DetailLevel: ReturnSummary, ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemsPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The number of disputes on each virtual page in the result set.
								The virtual page returned is determined by PageNumber.
								Default is 200.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<Details>DetailLevel: ReturnSummary, ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The page of the total result set returned in the call. The entire result set
								is virtual and the call returns only one page of it.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<Details>DetailLevel: ReturnSummary, ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DisputeFilterCount" type="ns:DisputeFilterCountType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The number of disputes that involve the requester as
								buyer or seller and match a given filter type.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<Details>DetailLevel: ReturnSummary, ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The result of the pagination, including the total number
								of virtual pages in the result set and the total number of
								disputes returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserDisputes</CallName>
									<Details>DetailLevel: ReturnSummary, ReturnAll, none</Details>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetUserPreferences -->
	<xs:element name="GetUserPreferencesRequest" type="ns:GetUserPreferencesRequestType"/>
	<xs:complexType name="GetUserPreferencesRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves the specified user preferences for the authenticated caller.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>SetUserPreferences</RelatedCalls>
				<SeeLink>
					<Title>Managing User Preferences</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingUserPreferences</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ShowBidderNoticePreferences" type="xs:boolean">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's preference for receiving contact
								information for unsuccessful bidders is returned in the response.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowCombinedPaymentPreferences" type="xs:boolean">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's combined payment preferences are
								returned in the response.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
								The CombinedPaymentPreferences.CombinedPaymentOption field is the only
								preference that should be managed with the GetUserPreferences and
								SetUserPreferences calls. All other Combined Payment preferences should be
								managed with the SetDiscountProfiles and GetDiscountProfiles calls.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowCrossPromotionPreferences" type="xs:boolean">
						<xs:annotation>
							<xs:documentation>
								This container should no longer be used as eBay Store Cross Promotions are no
								longer supported in the Trading API. This container will be removed from the
								Trading WSDL and API Call Reference docs in a future release.
								&lt;br&gt;&lt;br&gt;
								If included and set to true, the seller's cross-promotion preferences are
								returned in the response. These preferences are only applicable for eBay
								Store owners.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowSellerPaymentPreferences" type="xs:boolean">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's payment preferences are returned
								in the response.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowEndOfAuctionEmailPreferences" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's preferences for the end-of-auction
								email sent to the winning bidder is returned in the response. These
								preferences are only applicable for auction listings.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowSellerFavoriteItemPreferences" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's favorite item preferences are
								returned in the response.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowProStoresPreferences" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's ProStores preferences are
								returned in the response.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowEmailShipmentTrackingNumberPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's preference for sending an email to
								the buyer with the shipping tracking number is returned in the response.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowRequiredShipPhoneNumberPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's preference for requiring that the
								buyer supply a shipping phone number upon checkout is returned in the
								response. Some shipping carriers require the receiver's phone number.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowSellerExcludeShipToLocationPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, all of the seller's excluded shipping locations
								are returned in the response. The returned list mirrors the seller's current
								Exclude shipping locations list in My eBay's Shipping Preferences. An
								excluded shipping location in My eBay can be an entire geographical region
								(such as Middle East) or only an individual country (such as Iraq). Sellers
								can override these default settings for an individual listing by using the
								Item.ShippingDetails.ExcludeShipToLocation field in the AddItem family of
								calls.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowUnpaidItemAssistancePreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's Unpaid Item Assistant preferences
								are returned in the response. The Unpaid Item Assistant automatically opens
								an Unpaid Item dispute on the behalf of the seller.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
								To return the list of buyers excluded from the Unpaid Item Assistant
								mechanism, the ShowUnpaidItemAssistanceExclusionList field must also be
								included and set to true in the request. Excluded buyers can be viewed in
								the UnpaidItemAssistancePreferences.ExcludedUser field.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowPurchaseReminderEmailPreferences" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the seller's preference for sending a purchase
								reminder email to buyers is returned in the response.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
							  </CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowUnpaidItemAssistanceExclusionList" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If included and set to true, the list of eBay user IDs on the Unpaid Item
								Assistant Excluded User list is returned through the
								UnpaidItemAssistancePreferences.ExcludedUser field in the response. For
								excluded users, an Unpaid Item dispute is not automatically filed through
								the UPI Assistance mechanism. The Excluded User list is managed through the
								SetUserPreferences call.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
								To return the list of buyers excluded from the Unpaid Item Assistant
								mechanism, the ShowUnpaidItemAssistancePreference field must also be
								included and set to true in the request.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
							  </CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowSellerProfilePreferences" type="xs:boolean">
						<xs:annotation>
							<xs:documentation>
								If this flag is included and set to true, the seller's Business Policies profile information is
								returned in the response. This information includes a flag that indicates whether or
								not the seller has opted into Business Policies, as well as Business Policies profiles
								(payment, shipping, and return policy) active on the seller's account.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowSellerReturnPreferences" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If this flag is included and set to true, the seller's eBay Return Center
								preference information will be returned.
								&lt;br&gt;&lt;br&gt;
								eBay managed returns are currently only available on the US site. 
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowGlobalShippingProgramPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If this flag is included and set to true, the seller's preference for offering the Global Shipping Program to international buyers will be returned in &lt;strong&gt;OfferGlobalShippingProgramPreference&lt;/strong&gt;.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShowDispatchCutoffTimePreferences" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If this flag is included and set to true, the seller's same day handling cut off time is returned in &lt;strong&gt;DispatchCutoffTimePreference.CutoffTime&lt;/strong&gt;.
								&lt;br/&gt;&lt;br/&gt;
                        &lt;span class="tablenote"&gt;
                        &lt;strong&gt;Note:&lt;/strong&gt; Same day handling is available on the eBay Sandbox for release &lt;strong&gt;817&lt;/strong&gt;. It will become available on the production site as of Seller Release &lt;strong&gt;13.1&lt;/strong&gt;.
                        &lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>Specifying Shipping Services</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SameDayHandling</URL>
									<For>details about dispatch cut off times</For>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetUserPreferences -->
	<xs:element name="GetUserPreferencesResponse" type="ns:GetUserPreferencesResponseType"/>
	<xs:complexType name="GetUserPreferencesResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains some or all of the authenticated user's preferences. The preferences are
				grouped in sets and are returned according to the flag settings in the request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="BidderNoticePreferences" type="ns:BidderNoticePreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's preference for receiving contact
								information for unsuccessful bidders. This container is returned when
								&lt;b&gt;ShowBidderNoticePreferences&lt;/b&gt; is included and set to 'true' in
								the request. This preference is only applicable for auction listings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CombinedPaymentPreferences" type="ns:CombinedPaymentPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's combined payment preferences. This
								container is returned when &lt;b&gt;ShowCombinedPaymentPreferences&lt;/b&gt;
								is included and set to 'true' in the request.
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
								Calculated and flat-rate shipping preferences are no longer managed using the
								&lt;b&gt;SetUserPreferences&lt;/b&gt; and &lt;b&gt;GetUserPreferences&lt;/b&gt; calls.
								Instead,use the
								&lt;b&gt;SetDiscountProfiles&lt;/b&gt; and &lt;b&gt;GetDiscountProfiles&lt;/b&gt;
								calls to manage shipping discounts for combined payment orders.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CrossPromotionPreferences" type="ns:CrossPromotionPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container is no longer supported as eBay Store Cross Promotions are no
								longer supported in the Trading API. This container will be removed from the
								Trading WSDL and API Call Reference docs in a future release.
								&lt;br&gt;&lt;br&gt;
								Container consisting of the seller's cross-promotion preferences. This
								container is returned when &lt;b&gt;ShowCrossPromotionPreferences&lt;/b&gt; is
								included and set to 'true' in the request. These preferences are only applicable
								for eBay Store owners.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerPaymentPreferences" type="ns:SellerPaymentPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's payment preferences. This container is
								returned when &lt;b&gt;ShowSellerPaymentPreferences&lt;/b&gt; is included and
								set to 'true' in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerFavoriteItemPreferences" type="ns:SellerFavoriteItemPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's preferences for displaying items on a
								buyer's Favorite Sellers' Items page or Favorite Sellers' Items digest. This
								container is returned when &lt;b&gt;ShowSellerFavoriteItemPreferences&lt;/b&gt;
								is included and set to 'true' in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndOfAuctionEmailPreferences" type="ns:EndOfAuctionEmailPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's preferences for the end-of-auction email
								sent to the winning bidder. This container is returned when
								&lt;b&gt;ShowEndOfAuctionEmailPreferences&lt;/b&gt; is included and set to
								'true' in the request. These preferences are only applicable for auction
								listings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EmailShipmentTrackingNumberPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's preference for sending an email to the
								buyer with the shipping tracking number. This container is returned when
								&lt;b&gt;ShowEmailShipmentTrackingNumberPreference&lt;/b&gt; is included and set
								to 'true' in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RequiredShipPhoneNumberPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
									Container consisting of the seller's preference for requiring that the
									buyer supply a shipping phone number upon checkout. Some shipping carriers
									require the receiver's phone number. This container is returned when
									&lt;b&gt;ShowRequiredShipPhoneNumberPreference&lt;/b&gt; is included and set
									to 'true' in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>

					<xs:element name="ProStoresPreference" type="ns:ProStoresCheckoutPreferenceType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's ProStores preferences. This container
								is returned when &lt;b&gt;ShowProStoresPreference&lt;/b&gt; is included and
								set to 'true' in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UnpaidItemAssistancePreferences" type="ns:UnpaidItemAssistancePreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of a seller's Unpaid Item Assistant preferences. The
								Unpaid Item Assistant automatically opens an Unpaid Item dispute on the
								behalf of the seller. This container is returned if
								&lt;b&gt;ShowUnpaidItemAssistancePreference&lt;/b&gt; is included and set to
								'true' in the request.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
								To return the list of buyers excluded from the Unpaid Item Assistant
								mechanism, the &lt;b&gt;ShowUnpaidItemAssistanceExclusionList&lt;/b&gt; field
								must also be included and set to 'true' in the request. Excluded buyers can be
								viewed in the &lt;b&gt;UnpaidItemAssistancePreferences.ExcludedUser&lt;/b&gt;
								field.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerExcludeShipToLocationPreferences" type="ns:SellerExcludeShipToLocationPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of a list of the seller's excluded shipping locations.
								The returned list mirrors the seller's current Exclude shipping locations
								list in My eBay's shipping preferences. An excluded shipping location in My
								eBay can be an entire geographical region (such as Middle East) or only an
								individual country (such as Iraq). Sellers can override these default
								settings for an individual listing by using the
								&lt;b&gt;Item.ShippingDetails.ExcludeShipToLocation&lt;/b&gt; field in the
								Add/Revise/Relist calls. This container is returned if the
								&lt;b&gt;ShowSellerExcludeShipToLocationPreference&lt;/b&gt; field is included
								and set to 'true' in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PurchaseReminderEmailPreferences" type="ns:PurchaseReminderEmailPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of a seller's preference for sending a purchase reminder
								email to buyers. This container is returned if the
								&lt;b&gt;ShowPurchaseReminderEmailPreferences&lt;/b&gt; field is included and
								set to 'true' in the request.
						 	</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerThirdPartyCheckoutDisabled" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This flag is set with the
								&lt;b&gt;SellerThirdPartyCheckoutDisabled&lt;/b&gt; field of the
								&lt;b&gt;SetUserPreferences&lt;/b&gt; call, and is used to disable the
								use of a third-party application to handle the checkout flow for a seller.
								If true, Third-Party Checkout is disabled and any checkout flow initiated on
								the seller's application is redirected to the eBay checkout flow. This field
								is only returned if the &lt;b&gt;SellerThirdPartyCheckoutDisabled&lt;/b&gt;
								field has been set with the &lt;b&gt;SetUserPreferences&lt;/b&gt; call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									 <CallName>GetUserPreferences</CallName>
									 <Returned>Conditionally</Returned>
								</CallInfo>
						 	 </xs:appinfo>
						</xs:annotation>
					 </xs:element>
					 <xs:element name="SellerProfilePreferences" type="ns:SellerProfilePreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Parent response container consisting of high-level information for all
								Business Policies profiles defined for the user's account. This container is
								returned if &lt;b&gt;ShowSellerProfilePreferences&lt;/b&gt; is included and
								set to 'true' in the &lt;b&gt;GetUserPreferences&lt;/b&gt; request (and one or
								more Business Policies profiles are defined for the user's account).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerReturnPreferences" type="ns:SellerReturnPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of a seller's eBay Return Center preferences. This
								container is returned if &lt;b&gt;ShowSellerReturnPreferences&lt;/b&gt; is
								included and set to true in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OfferGlobalShippingProgramPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
									This flag indicates whether the seller has opted in to the Global Shipping Program and is able to offer global shipping to international buyers. Returned when &lt;strong&gt;ShowGlobalShippingProgramPreference&lt;/strong&gt; is included and set to true.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetUserPreferences</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DispatchCutoffTimePreference" type="ns:DispatchCutoffTimePreferencesType" minOccurs="0">
   					<xs:annotation>
   						<xs:documentation>
								Contains information about a seller's order cut off time preferences for same day shipping. If the seller specifies a value of &lt;code&gt;0&lt;/code&gt; in &lt;strong&gt;Item.DispatchTimeMax&lt;/strong&gt; to offer same day handling when listing an item, the seller's shipping time commitment depends on the order cut off time set for the listing site, as indicated by &lt;strong&gt;DispatchCutoffTimePreference.CutoffTime&lt;/strong&gt;.
								&lt;br/&gt;&lt;br/&gt;
                        &lt;span class="tablenote"&gt;
                        &lt;strong&gt;Note:&lt;/strong&gt; Same day handling is available on the eBay Sandbox for release &lt;strong&gt;817&lt;/strong&gt;. It will become available on the production site as of Seller Release &lt;strong&gt;13.1&lt;/strong&gt;.
                        &lt;/span&gt;
   						</xs:documentation>
   						<xs:appinfo>
   							<CallInfo>
   								<CallName>GetUserPreferences</CallName>
   								<Returned>Conditionally</Returned>
   							</CallInfo>
								<SeeLink>
									<Title>Specifying Shipping Services</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SameDayHandling</URL>
									<For>details about dispatch cut off times</For>
								</SeeLink>
   						</xs:appinfo>
   					</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetVeROReasonCodeDetails -->
	<xs:element name="GetVeROReasonCodeDetailsRequest" type="ns:GetVeROReasonCodeDetailsRequestType"/>
	<xs:complexType name="GetVeROReasonCodeDetailsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves details for VeRO reason codes and their descriptions. You can specify a 
				reason code ID to get details for a specific reason on the site specified in the 
				request header. If ReasonCodeID is not passed in the request, all reason codes are 
				returned. Set ReturnAllSites to true to retrieve reason codes for all sites.
				You must be a member of the Verified Rights Owner (VeRO) Program to use this call. 
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Retrieves details about VeRO reason codes for a given site or all sites. You must 
					be a member of the Verified Rights Owner (VeRO) Program to use this call. 
				</Summary>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ReasonCodeID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
				 				Unique identifier for a reason code. If this ReasonCodeID is passed then 
				 				only details of this ReasonCodeID will be returned. If no reason code is 
				 				specified, all reason codes are returned.
							</xs:documentation>
							<xs:appinfo>
								<Min/>
								<Max/>
								<Default/>
								<CallInfo>
									<CallName>GetVeROReasonCodeDetails</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReturnAllSites" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
					 			Set to true to retrieve reason codes for all sites. If not specified, 
					 			reason codes are returned for the site specified in the request header 
					 			only. 
					 			If ReasonCodeID is specified, this parameter is ignored.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetVeROReasonCodeDetails</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetVeROReasonCodeDetails -->
	<xs:element name="GetVeROReasonCodeDetailsResponse" type="ns:GetVeROReasonCodeDetailsResponseType"/>
	<xs:complexType name="GetVeROReasonCodeDetailsResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the reason codes for all sites. 
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="VeROReasonCodeDetails" type="ns:VeROReasonCodeDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the list of the status codes for a site.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetVeROReasonCodeDetails</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetVeROReportStatus -->
	<xs:element name="GetVeROReportStatusRequest" type="ns:GetVeROReportStatusRequestType"/>
	<xs:complexType name="GetVeROReportStatusRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves status information about VeRO reported items you have submitted. You 
				can receive the status of individual items you have reported or, by specifying 
				VeROReportPacketID, you can retrieve status for all items reported with a given 
				VeROReportItems request. You can also retrieve items that were reported during a 
				given time period. If no input parameters are specified, status is returned on all 
				items you have reported in the last two years.
				You must be a member of the Verified Rights Owner (VeRO) Program to use this 
				call.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Retrieves status information about VeRO reported items. You must be a member of 
					the Verified Rights Owner (VeRO) Program to use this call.
				</Summary>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="VeROReportPacketID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Packet identifier associated with the reported items for which you want to 
								retrieve status. By default, reported item details are not returned when 
								you specify the packet ID in the request. Applies only to items reported 
								with VeROReportItems. 
							</xs:documentation>
							<xs:appinfo>
								<Min/>
								<Max/>
								<Default/>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Item ID for an item reported for alleged infringement. Applies to items 
								reported with VeROReportItems or by other means (e.g., through the 
								web flow).
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="IncludeReportedItemDetails" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Set to true to return reported item details when you specify VeROReportPacketID in the request.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TimeFrom" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Limits returned items to only those that were submited on or after the 
								date-time specified. If specified, TimeTo must also be specified. 
								Express the date-time in the format YYYY-MM-DD HH:MM:SS, and in GMT.
								(For information on how to convert between your local time zone
								and GMT, see Time Values Note.) Applies to items reported with 
								VeROReportItems or by other means (e.g., through the web flow).
								Infringement reporting data is maintained for two years after the date of 
								submission. 
								This field is ignored if VeROReportPacketID or ItemID is specified. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TimeTo" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Limits returned items to only those that were submited on or before the 
								date-time specified. If specified, TimeFrom must also be specified. 
								Express date-time in the format YYYY-MM-DD HH:MM:SS, and in GMT.
								(For information on how to convert between your local time zone
								and GMT, see Time Values Note.) Applies to items reported with 
								VeROReportItems or by other means (e.g., through the web flow).
								Infringement reporting data is maintained for two years after the date of 
								submission. 
								This field is ignored if VeROReportPacketID or ItemID is specified.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the data controlling the pagination of the returned values: how
								many items are returned per page of data (per call) and the number of the 
								page to return with the current call.
								</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetVeROReportStatus -->
	<xs:element name="GetVeROReportStatusResponse" type="ns:GetVeROReportStatusResponseType"/>
	<xs:complexType name="GetVeROReportStatusResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains status information for items reported by the VeRO Program member. 
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains information regarding the pagination of data (if pagination is
								used), including total number of pages and total number of entries.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMoreItems" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, there are more items yet to be retrieved. Additional
								calls with higher page numbers or more items per page must
								be made to retrieve these items. Not returned if no items match the
								request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemsPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the maximum number of ItemType objects that can be returned in
								ReportedItemDetails for any given call.
							</xs:documentation>
							<xs:appinfo>
								<Min>1</Min>
								<Max>200</Max>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the page of data returned by the current call. For instance,
								for the first set of items can be returned, this field has a value of
								one.
							</xs:documentation>
							<xs:appinfo>
								<Min>1</Min>
								<Max/>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VeROReportPacketID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The packet ID for status being returned.
							</xs:documentation>
							<xs:appinfo>
								<Min/>
								<Max/>
								<Default/>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VeROReportPacketStatus" type="ns:VeROReportPacketStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Status of the packet. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReportedItemDetails" type="ns:VeROReportedItemDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the list of the reported item details.
								Returns empty if no items are available that match the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetVeROReportStatus</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetWantItNowPost -->
	<xs:element name="GetWantItNowPostRequest" type="ns:GetWantItNowPostRequestType"/>
	<xs:complexType name="GetWantItNowPostRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves data for a specific, active Want It Now post identified by a post ID.
				The response includes the following fields: CategoryID, Description, PostID,
				Site, StartTime, ResponseCount, and Title. Although GetWantItNowSearchResults
				returns most of this information, only GetWantItNowPost returns Description for
				a post.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Want It Now</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=WantItNowChapter</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="PostID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the post ID that uniquely identifies the Want It Now post for
								which to retrieve the data. PostID is a required input. PostID is unique
								across all eBay sites.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowPost</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetWantItNowPost -->
	<xs:element name="GetWantItNowPostResponse" type="ns:GetWantItNowPostResponseType"/>
	<xs:complexType name="GetWantItNowPostResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the Want It Now post data returned by the call. The data for the
				specified post listing is returned in a WantItNowPostType object.
 			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="WantItNowPost" type="ns:WantItNowPostType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the data defining a single Want It Now post.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowPost</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetWantItNowSearchResults -->
	<xs:element name="GetWantItNowSearchResultsRequest" type="ns:GetWantItNowSearchResultsRequestType"/>
	<xs:complexType name="GetWantItNowSearchResultsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves a list of active Want It Now posts that match specified keywords
				and/or a specific category ID. The response contains the following data:
				CategoryID, PostID, StartTime, ResponseCount, Site, and Title. To get the post
				description (Description), you must use GetWantItNowPost to retrieve individual
				posts.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Want It Now</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=WantItNowChapter</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Limits the result set to just those Want It Now posts listed in the
								specified category. Defaults to all categories if no category ID is
								specified. If the specified category ID does not match an existing
								category for the site, an invalid-category error message is returned.
								Controls the set of listings to return (not the details to return for each
								listing).
								You must specify a Query and/or a CategoryID in the request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Query" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies a search string. The search string consists of one or more
								keywords to search for in the listing title. Note that the post
								description will also be searched if SearchInDescription is enabled.
								By default, requests return a list of Want It Now posts that include all
								of the keywords specified in the Query. All words used in the query,
								including "and," "or," and "the,"  will be treated as keywords. You can,
								however, use modifiers and wildcards (e.g., +, -, and *) in the Query
								field to create more complex searches. Be careful when using spaces before
								or after modifiers and wildcards (+, -, or *), as the spaces can affect
								the query logic.
								See the eBay Web Services Guide for a list of valid search keyword query
								operators and examples.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>350 (characters)</MaxLength>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SearchInDescription" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, include the description field of Want It Now posts in the keyword search. Want
								It Now posts returned are those where specified search keywords appear in
								either the description or the title. This is the default behavior if SearchInDescription
								is not specified. If false, only the title will be searched. SearchInDescription is an
								optional input.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SearchWorldwide" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, the search applies to all eBay sites. If false, the search is
								limited to the site specified in the URL query string when the call is
								made.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Pagination" type="ns:PaginationType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Controls the pagination of the result set. Child elements specify the
								maximum number of item listings to return per call and which page of data
								to return.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GetWantItNowSearchResults -->
	<xs:element name="GetWantItNowSearchResultsResponse" type="ns:GetWantItNowSearchResultsResponseType">
		<xs:annotation>
			<xs:documentation>
				Response contains the Want It Now posts that have the specified keyword(s) in the
				title and (optionally) the description.
			</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="GetWantItNowSearchResultsResponseType">
		<xs:annotation>
			<xs:documentation>
				Response contains the Want It Now posts that have the specified keyword(s) in the
				title and (optionally) the description.
 			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="WantItNowPostArray" type="ns:WantItNowPostArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the returned Want It Now posts, if any. The data for each post is
								returned in a WantItNowPostType object.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="HasMoreItems" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether there are additional Want It Now posts that meet the
								search criteria.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemsPerPage" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the maximum number of Want It Now posts that can be returned in
								a WantItNowPostArray for a request. This value can be specified in the
								request by  EntriesPerPage in Pagination in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PageNumber" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the page of data returned by the current call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaginationResult" type="ns:PaginationResultType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the results of the pagination, including the total number of
								pages of data there are to be returned and the total number of posts there
								are to be returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GetWantItNowSearchResults</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GeteBayDetails -->
	<xs:element name="GeteBayDetailsRequest" type="ns:GeteBayDetailsRequestType"/>
	<xs:complexType name="GeteBayDetailsRequestType">
		<xs:annotation>
			<xs:documentation>
				Retrieves eBay IDs and codes (e.g., site IDs and shipping service
				codes), enumerated data (e.g., payment methods), and other common eBay
				meta-data. This call enables you to keep certain data up to date in your
				applications without referring to the schema, the documentation, or the
				eBay online help. Other data is returned for your reference, but you may
				need to refer to the schema or the documentation for information about
				valid values and usage.
				&lt;br&gt;&lt;br&gt;
				In some cases, the data returned in the response will vary according to
				the site that you use for the request.
				&lt;br&gt;&lt;br&gt;
				If you use GeteBayDetails in preparation for listing in the US Motors Parts
				and Accessories categories, use site ID 0 (which is the site ID of the US
				site) when you call GeteBayDetails.
				&lt;br&gt;&lt;br&gt;
				Sellers who engage in cross-border trade on sites that require a recoupment agreement, must agree to the
				recoupment terms before adding items to the site. This agreement allows eBay to reimburse
				a buyer during a dispute and then recoup the cost from the seller. Information about whether a site
        is a recoupment site is returned in the GeteBayDetailsResponse.RecoupmentPolicyDetails container.
			</xs:documentation>
			<xs:appinfo>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="DetailName" type="ns:DetailNameCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								A designation of what kind of information you wish returned for the
								specified eBay site. If omitted, all details are returned. The
								possible values for input (the enumeration values of
								DetailNameCodeType) are the same name as fields returned by the
								response. See the documentation for the GeteBayDetails response to
								better understand the DetailName options.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GeteBayDetails -->
	<xs:element name="GeteBayDetailsResponse" type="ns:GeteBayDetailsResponseType">
		<xs:annotation>
			<xs:documentation>
				Details about a specified site in response to &lt;b&gt;GeteBayDetailsRequest&lt;/b&gt;. 
				If no &lt;b&gt;DetailName&lt;/b&gt;
				field is identified in the request, all elements of &lt;b&gt;GeteBayDetailsResponse&lt;/b&gt; are
				returned. Otherwise, eBay returns only the elements corresponding to the specified
				&lt;b&gt;DetailName&lt;/b&gt; fields. UpdateTime gives the time of modification of the most recently
				modified &lt;b&gt;DetailName&lt;/b&gt;.
			</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="GeteBayDetailsResponseType">
		<xs:annotation>
			<xs:documentation>
				Details about a specified site in response to &lt;b&gt;GeteBayDetailsRequest&lt;/b&gt;. 
				If no &lt;b&gt;DetailName&lt;/b&gt;
				field is identified in the request, all elements of &lt;b&gt;GeteBayDetailsResponse&lt;/b&gt; are
				returned. Otherwise, eBay returns only the elements corresponding to the specified
				&lt;b&gt;DetailName&lt;/b&gt; fields. &lt;b&gt;UpdateTime&lt;/b&gt; gives the time of modification of the most recently
				modified &lt;b&gt;DetailName&lt;/b&gt;.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CountryDetails" type="ns:CountryDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the country code and associated name of the countries supported by
								the eBay system, regardless of the site specified in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CurrencyDetails" type="ns:CurrencyDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the currencies supported by the eBay system, regardless of the site
								specified in the request.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;CurrencyDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; filters are 
								used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;								
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DispatchTimeMaxDetails" type="ns:DispatchTimeMaxDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								A dispatch time specifies the maximum number of business days a seller commits
								to for shipping an item to domestic buyers after receiving a cleared payment.
								Returns all dispatch times in the system, regardless of the site specified in
								the request.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;DispatchTimeMaxDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaymentOptionDetails" type="ns:PaymentOptionDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;Deprecated &lt;/b&gt;	&lt;br /&gt;
								Use &lt;b&gt;GetCategoryFeatures&lt;/b&gt; instead, and pass in 
								&lt;b&gt;PaymentMethods&lt;/b&gt; as a &lt;b&gt;FeatureID&lt;/b&gt; value in the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<SeeLink>
										<Title>GetCategoryFeatures</Title>
										<URL>GetCategoryFeatures.html</URL>
									</SeeLink>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RegionDetails" type="ns:RegionDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								No longer returned; replaced by &lt;b&gt;ShippingLocationDetails&lt;/b&gt;.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<Ignore/>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
								<SeeLink>
									<Title>ShippingLocationDetails</Title>
									<URL>#Response.ShippingLocationDetails</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingLocationDetails" type="ns:ShippingLocationDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the regions and locations supported by eBay's shipping services. Returns
								all shipping locations supported by eBay, regardless of the site specified in
								the request.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;ShippingLocationDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingServiceDetails" type="ns:ShippingServiceDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the shipping services supported by the specified eBay site. Returns only
								the shipping services that are applicable to the site specified in the
								request.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;ShippingServiceDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SiteDetails" type="ns:SiteDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists all available eBay sites and their associated SiteID numbers.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;SiteDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TaxJurisdiction" type="ns:TaxJurisdictionType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Details the different tax jurisdictions or tax regions applicable to the
								site specified in the request.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;TaxJurisdiction&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
							<SeeLink>
								<Title>TaxTable.TaxJurisdiction in SetTaxTable</Title>
								<URL>SetTaxTable.html#Request.TaxTable.TaxJurisdiction</URL>
							</SeeLink>
							<SeeLink>
								<Title>Item.UseTaxTable in AddItem</Title>
								<URL>AddItem.html#Request.Item.UseTaxTable</URL>
							</SeeLink>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="URLDetails" type="ns:URLDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists eBay URLs that are applicable to the site specified in the request.\
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;URLDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TimeZoneDetails" type="ns:TimeZoneDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the details of the time zones supported by the eBay system.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;TimeZoneDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemSpecificDetails" type="ns:ItemSpecificDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The site's validation rules (e.g., string lengths) for custom Item Specifics.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;ItemSpecificDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UnitOfMeasurementDetails" type="ns:UnitOfMeasurementDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the suggested unit-of-measurement strings to use with Item Specifics
								descriptions.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;UnitOfMeasurementDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RegionOfOriginDetails" type="ns:RegionOfOriginDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								No longer returned.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<Ignore/>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingPackageDetails" type="ns:ShippingPackageDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the various shipping packages supported by the specified site.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
							  This container is only returned if &lt;b&gt;ShippingPackageDetails&lt;/b&gt; is included as a 
							  &lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
							  filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingCarrierDetails" type="ns:ShippingCarrierDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the shipping carriers supported by the specified site.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;ShippingCarrierDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReturnPolicyDetails" type="ns:ReturnPolicyDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Lists the return policies supported by the eBay site specified in the request.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;ReturnPolicyDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingStartPriceDetails" type="ns:ListingStartPriceDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the minimum starting prices for the supported types of eBay listings.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;ListingStartPriceDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.								
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BuyerRequirementDetails" type="ns:SiteBuyerRequirementDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Details various eBay-buyer requirements.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingFeatureDetails" type="ns:ListingFeatureDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Details the listing features available for the site specified in the request.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;ListingFeatureDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
								</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VariationDetails" type="ns:VariationDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Site-level validation rules for multi-variation listings (for example, the
								maximum number of variations per listing). Use &lt;b&gt;GetCategoryFeatures&lt;/b&gt; to
								determine which categories on a site support variations. Use
								&lt;b&gt;GetCategorySpecifics&lt;/b&gt; for rules related to recommended or required variation
								specifics.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;VariationDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>GetCategoryFeatures</Title>
									<URL>GetCategoryFeatures.html#Response.Category.VariationsEnabled</URL>
								</SeeLink>
								<SeeLink>
									<Title>GetCategorySpecifics</Title>
									<URL>GetCategorySpecifics.html</URL>
								</SeeLink>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExcludeShippingLocationDetails" type="ns:ExcludeShippingLocationDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Lists the locations supported by the &lt;b&gt;ExcludeShipToLocation&lt;/b&gt; feature. These are
								locations that a seller can list as areas where they will not ship an item.
								&lt;br /&gt;
								The codes reflect the &lt;a href=
								"http://www.iso.org/iso/country_codes/iso_3166_code_lists/english_country_names_and_code_elements.htm"
								&gt;ISO 3166&lt;/a&gt; location codes.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UpdateTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The time of the most recent modification to any feature detail. If specific
								feature details are passed in the request, gives the most recent modification time
								of those feature details.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RecoupmentPolicyDetails" type="ns:RecoupmentPolicyDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Details the recoupment policies for the site specified in the request.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;RecoupmentPolicyDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingCategoryDetails" type="ns:ShippingCategoryDetailsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								A shipping service category supported for the site.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note: &lt;/b&gt;
								This container is only returned if &lt;b&gt;ShippingCategoryDetails&lt;/b&gt; is included as a 
								&lt;b&gt;DetailName&lt;/b&gt; filter in the request, or if no &lt;b&gt;DetailName&lt;/b&gt; 
								filters are used in the request.
								&lt;/span&gt;  &lt;br/&gt;&lt;br/&gt;
								Each shipping service supported for a site is automatically categorized by eBay into one of the 
								shipping categories available for that site depending on how the shipping service shipping time
								aligns with the shipping times specified by eBay for each category. 
								&lt;br&gt;&lt;br&gt;
								Notice that you cannot specify a ShippingCategory 
								as an input to any API call - eBay does this categorizing automatically. ShippingCategory is read-only data 
								that is returned in the &lt;b&gt;ShippingServiceDetails&lt;/b&gt; container. One possible use of this data is to segregate shipping
								services by ShippingCategory in a pick list. (For an example of this, see the Services pulldown menu in the 
								Give buyers shipping details form in the eBay Sell Your Item flow.) 
								&lt;br&gt;&lt;br&gt;
								One way to populate the picklist would be to call &lt;b&gt;GeteBayDetails&lt;/b&gt; 
								with &lt;b&gt;DetailName&lt;/b&gt; set to &lt;b&gt;ShippingServiceDetails&lt;/b&gt;.
								Then sort these results by ShippingCategory and populate the picklist.						
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>GeteBayDetails</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GeteBayOfficialTime -->
	<xs:element name="GeteBayOfficialTimeRequest" type="ns:GeteBayOfficialTimeRequestType"/>
	<xs:complexType name="GeteBayOfficialTimeRequestType">
		<xs:annotation>
			<xs:documentation>
				Gets the official eBay system time in GMT.
			</xs:documentation>
			<xs:appinfo>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: GeteBayOfficialTime -->
	<xs:element name="GeteBayOfficialTimeResponse" type="ns:GeteBayOfficialTimeResponseType"/>
	<xs:complexType name="GeteBayOfficialTimeResponseType">
		<xs:annotation>
			<xs:documentation>
				The Timestamp field indicates the official eBay system time in GMT.
				For information about converting between GMT and other time zones,
				see "Time Values" in the Data Types appendix in the eBay Web Services guide.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: IssueRefund -->
	<xs:element name="IssueRefundRequest" type="ns:IssueRefundRequestType"/>
	<xs:complexType name="IssueRefundRequestType">
		<xs:annotation>
			<xs:documentation>
				&lt;b&gt;Half.com only.&lt;/b&gt;&amp;nbsp;Issues a refund for a specific
				Half.com order line item. This can only be called by a seller. Sellers do not
				have the ability to issue a general refund (a refund not tied to an order line
				item) to a buyer.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Half.com</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=HalfOverview</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for the Half.com item listing. Unless an
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is specified in the &lt;b&gt;IssueRefund&lt;/b&gt; request, the &lt;b&gt;ItemID&lt;/b&gt; is
								required along with the corresponding &lt;b&gt;TransactionID&lt;/b&gt; to identify the
								order line item that will be refunded. You can use &lt;b&gt;GetSellerPayments&lt;/b&gt; to
								retrieve the &lt;b&gt;ItemID&lt;/b&gt; and/or &lt;b&gt;TransactionID&lt;/b&gt; associated with the order line
								item.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for a Half.com order line item (transaction). An order
								line item is created once there is a commitment from a buyer to purchase
								an item. Along with its corresponding &lt;b&gt;ItemID&lt;/b&gt;, a &lt;b&gt;TransactionID&lt;/b&gt; is used to
								identify the order line item that will be refunded. Unless an
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is specified in the &lt;b&gt;IssueRefund&lt;/b&gt; request, the
								&lt;b&gt;TransactionID&lt;/b&gt; is required along with the corresponding &lt;b&gt;ItemID&lt;/b&gt;. You can
								use &lt;b&gt;GetSellerPayments&lt;/b&gt; to retrieve the &lt;b&gt;ItemID&lt;/b&gt; and/or &lt;b&gt;TransactionID&lt;/b&gt;
								associated with the order line item.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RefundReason" type="ns:RefundReasonCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Explanation of the reason that the refund is being issued.
						</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RefundType" type="ns:RefundTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Explanation of the costs that the refund amount covers.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RefundAmount" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The amount the seller wants to refund to the buyer, in US Dollars (USD).
								Must be greater than 0.00. Half.com allows a maximum of the original item
								sale price (order line item price plus original shipping reimbursement) plus
								return shipping costs (the amount the buyer paid to return the item).
								Typically, the return shipping cost is based on the current cost of
								shipping the individual item (not the discounted cost calculated during
								the original checkout for a Combined Payment order). You can also issue a
								partial refund for the amount you want the buyer to receive. If
								RefundType=Full or RefundType=FullPlusShipping and you do not pass
								&lt;b&gt;RefundAmount&lt;/b&gt; in the request, Half.com will calculate the refund amount for
								you. If you pass &lt;b&gt;RefundAmount&lt;/b&gt; in the request, the amount you specify will
								override Half.com's calculated value. Required if RefundType=
								CustomOrPartial.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RefundMessage" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Note to the buyer. Cannot include HTML.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>400</MaxLength>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for an eBay order line item. This field is created
								as soon as there is a commitment to buy from the seller, and its value
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. The &lt;b&gt;OrderLineItemID&lt;/b&gt; value is used to
								identify the order line item that will be refunded. Unless an
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is specified in the &lt;b&gt;IssueRefund&lt;/b&gt; request, the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is required. You can use &lt;b&gt;GetSellerPayments&lt;/b&gt; to retrieve
								the &lt;b&gt;OrderLineItemID&lt;/b&gt; associated with the order line item.
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50 (Note: ItemIDs and TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: IssueRefund -->
	<xs:element name="IssueRefundResponse" type="ns:IssueRefundResponseType"/>
	<xs:complexType name="IssueRefundResponseType">
		<xs:annotation>
			<xs:documentation>
Indicates the refund amount that a seller issued to a buyer for a single Half.com order line item.
Refunds may only be issued for a specific order line item. Sellers do not have the ability to issue a 
general refund (not tied to an order line item) to a buyer.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="RefundFromSeller" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Total amount that the seller asked Half.com to refund to 
							a buyer for a Half.com order line item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TotalRefundToBuyer" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Total amount that Half.com refunded to the buyer (which could include the refund amount 
							from the seller plus a refund amount from Half.com).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>IssueRefund</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: LeaveFeedback -->
	<xs:element name="LeaveFeedbackRequest" type="ns:LeaveFeedbackRequestType"/>
	<xs:complexType name="LeaveFeedbackRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a buyer and seller to leave feedback for their order partner at the
				conclusion of a successful order. Feedback is left at the order line item level, 
				so multiple line item orders may have multiple Feedback entries.&amp;nbsp;&lt;b&gt;
				Also for Half.com&lt;/b&gt;.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetFeedback, GetSellerDashboard, GetSellerTransactions</RelatedCalls>
				<SeeLink>
					<Title>Leaving and Retrieving Feedback</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Feedback</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Feedback</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeedbackIntro</URL>
				</SeeLink>
				<SeeLink>
					<Title>Leaving Feedback for Another User</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeedbackLeave</URL>
				</SeeLink>
				<SeeLink>
					<Title>Detailed Seller Ratings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=DetailedSellerRatings</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. A listing can have multiple
								order line items, but only one &lt;b&gt;ItemID&lt;/b&gt;. Unless an
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is specified in the &lt;b&gt;LeaveFeedback&lt;/b&gt; request, the &lt;b&gt;ItemID&lt;/b&gt; is
								required along with the &lt;b&gt;TargetUser&lt;/b&gt; to identify an order line item
								existing between the caller and the &lt;b&gt;TargetUser&lt;/b&gt; that requires feedback. A
								Feedback entry will be posted for this order line item. If there are
								multiple order line items between the two order partners that still
								require feedback, the &lt;b&gt;TransactionID&lt;/b&gt; will also be required to isolate the
								targeted order line item. Feedback cannot be left for order line items
								with creation dates more than 60 days in the past.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>LeaveFeedback</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CommentText" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Textual comment that explains, clarifies, or justifies the Feedback rating
								specified in &lt;b&gt;CommentType&lt;/b&gt;. 
								&lt;br&gt;&lt;br&gt; 
								This comment will still be displayed even if submitted Feedback is withdrawn.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>80</MaxLength>
								<CallInfo>
									<CallName>LeaveFeedback</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CommentType" type="ns:CommentTypeCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>LeaveFeedback</CallName>
									<AllValuesExcept>Withdrawn, IndependentlyWithdrawn</AllValuesExcept>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay order line item (transaction). If there
								are multiple order line items between the two order partners that still
								require feedback, the &lt;b&gt;TransactionID&lt;/b&gt; is required along with the
								corresponding &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TargetUser&lt;/b&gt; to isolate the targeted order line
								item. If an &lt;b&gt;OrderLineItemID&lt;/b&gt; is included in the response to identify a
								specific order line item, none of the preceding fields (&lt;b&gt;ItemID&lt;/b&gt;,
								&lt;b&gt;TransactionID&lt;/b&gt;, &lt;b&gt;TargetUser&lt;/b&gt;) are needed. Feedback cannot be left for order
								line items with creation dates more than 60 days in the past.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>LeaveFeedback</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TargetUser" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This eBay User ID identifies the recipient user for whom the feedback is being
								left.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>LeaveFeedback</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerItemRatingDetailArray" type="ns:ItemRatingDetailArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container for detailed seller ratings (DSRs). If a buyer is providing DSRs,
								they are specified in this container. Sellers have access to the number of
								ratings they've received, as well as to the averages of the DSRs they've
								received in each DSR area (i.e., to the average of ratings in the
								item-description area, etc.).
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>Detailed Seller Ratings</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=DetailedSellerRatings</URL>
								</SeeLink>
								<CallInfo>
									<CallName>LeaveFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier for an eBay order line item and
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. If an &lt;b&gt;OrderLineItemID&lt;/b&gt; is included in
								the request, the &lt;b&gt;ItemID&lt;/b&gt;, &lt;b&gt;TransactionID&lt;/b&gt;, and &lt;b&gt;TargetUser&lt;/b&gt; fields are not
								required. Feedback cannot be left for order line items with creation
								dates more than 60 days in the past. 
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>100</MaxLength>
								<CallInfo>
									<CallName>LeaveFeedback</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: LeaveFeedback -->
	<xs:element name="LeaveFeedbackResponse" type="ns:LeaveFeedbackResponseType"/>
	<xs:complexType name="LeaveFeedbackResponseType">
		<xs:annotation>
			<xs:documentation>
          LeaveFeedback response message includes an acknowledgement if the
          feedback was successfully left.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="FeedbackID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the feedback that has been left.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>LeaveFeedback</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: MoveSellingManagerInventoryFolder -->
	<xs:element name="MoveSellingManagerInventoryFolderRequest" type="ns:MoveSellingManagerInventoryFolderRequestType"/>
	<xs:complexType name="MoveSellingManagerInventoryFolderRequestType">
		<xs:annotation>
			<xs:documentation>
			  Moves a Selling Manager inventory folder.
				&lt;br&gt;&lt;br&gt;
				This call is subject to change without notice; the deprecation process is
				inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="FolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Unique ID of the folder that will be moved. User can retrieve the FolderId
								using GetSellingManagerInventoryFolder.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>MoveSellingManagerInventoryFolder</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NewParentFolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  Unique folder ID for the new parent folder. If no NewParentFolderID is
								submitted, the folder is moved to the root level.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>MoveSellingManagerInventoryFolder</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: MoveSellingManagerInventoryFolder -->
	<xs:element name="MoveSellingManagerInventoryFolderResponse" type="ns:MoveSellingManagerInventoryFolderResponseType"/>
	<xs:complexType name="MoveSellingManagerInventoryFolderResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of move folder operation.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: PlaceOffer -->
	<xs:element name="PlaceOfferRequest" type="ns:PlaceOfferRequestType"/>
	<xs:complexType name="PlaceOfferRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables the authenticated user to to make a bid, a best offer, or
				a purchase on the item specified by the ItemID input field.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Enabling Best Offer</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EnablingBestOffer</URL>
				</SeeLink>
				<SeeLink>
					<Title>API License Agreement</Title>
					<URL>http://developer.ebay.com/join/licenses/Default.aspx</URL>
				</SeeLink>
				<SeeLink>
					<Title>eBay User Agreement</Title>
					<URL>http://pages.ebay.com/help/policies/user-agreement.html</URL>
				</SeeLink>
				<SeeLink>
					<Title>PlaceOffer API License Agreement Addendum</Title>
					<URL>http://developer.ebay.com/terms/PlaceOffer_API_License_Addendum_uv.pdf</URL>
				</SeeLink>
				<SeeLink>
					<Title>API Logo Usage Requirements</Title>
					<URL>http://developer.ebay.com/join/licenses/apilogousage</URL>
				</SeeLink>
				<SeeLink>
					<Title>Filing a Support Ticket</Title>
					<URL>http://developer.ebay.com/support/developersupport/request</URL>
				</SeeLink>
				<SeeLink>
					<Title>eBay Partner Network</Title>
					<URL>https://www.ebaypartnernetwork.com/</URL>
				</SeeLink>
				<RelatedCalls>GetChallengeToken, GetBestOffers</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Offer" type="ns:OfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the type of offer being made. If the item is a
								competitive-bidding listing, the offer is a bid. If the item is a
								fixed-price listing, then the offer purchases the item. If the item is a
								competitive-bidding listing and the offer is of type with an active,
								unexercised Buy It Now option, then the offer can either purchase the
								item or be a bid. See the schema documentation for OfferType for details
								on its properties and their meanings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique item ID that identifies the item listing for which the action is being
								submitted.
								&lt;br&gt;&lt;br&gt;
								If the item was listed with Variations, you must also specify
								VariationSpecifics in the request to uniquely identify the
								variant being purchased.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BlockOnWarning" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If a warning message exists and BlockOnWarning is true,
								the warning message is returned and the bid is blocked. If no warning message
								exists and BlockOnWarning is true, the bid is placed. If BlockOnWarning
								is false, the bid is placed, regardless of warning.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AffiliateTrackingDetails" type="ns:AffiliateTrackingDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container for affiliate-related tags, which enable the tracking of user
								activity. If you include AffiliateTrackingDetails in your PlaceOffer call, then
								it is possible to receive affiliate commissions based on calls made by your
								application. (See the &lt;a href=
								"http://www.ebaypartnernetwork.com/" target="_blank"&gt;eBay Partner Network&lt;/a&gt;
								for information about commissions.) Please note that affiliate tracking is not
								available in the Sandbox environment, and that affiliate tracking is not
								available when you make a best offer.
							</xs:documentation>
							<xs:appinfo>
								<SeeLink>
									<Title>Affiliate Tracking Concepts</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=AffiliateTrackingConcepts</URL>
								</SeeLink>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VariationSpecifics" type="ns:NameValueListArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Name-value pairs that identify a single variation within the
								listing identified by ItemID. Required when the seller
								listed the item with Item Variations.&lt;br&gt;
								&lt;br&gt;
								If you want to buy items from multiple variations in the same
								listing, use a separate PlaceOffer request for each variation.
								For example, if you want to buy 3 red shirts and 2 black shirts
								from the same listing, use one PlaceOffer request for the
								3 red shirts, and another PlaceOffer request for the 2
								black shirts.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: PlaceOffer -->
	<xs:element name="PlaceOfferResponse" type="ns:PlaceOfferResponseType"/>
	<xs:complexType name="PlaceOfferResponseType">
		<xs:annotation>
			<xs:documentation>
				The &lt;b&gt;PlaceOffer&lt;/b&gt; response notifies you about the success and result
				of the call.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SellingStatus" type="ns:SellingStatusType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the current bidding/purchase state of the item listing regarding
								the offer extended using &lt;b&gt;PlaceOffer&lt;/b&gt;. See the schema documentation for
								the &lt;b&gt;SellingStatus&lt;/b&gt; object, the properties of which contain such
								post-offer information as the current high bidder, the current price for
								the item, and the bid increment.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay order line item (transaction). The
								&lt;b&gt;TransactionID&lt;/b&gt; field is only returned if the &lt;b&gt;Offer.Action&lt;/b&gt; field was set
								to &lt;b&gt;Purchase&lt;/b&gt; in the input and the purchase was successful. A Purchase
								action in &lt;b&gt;PlaceOffer&lt;/b&gt; can be used for a fixed-price listing, or for an
								auction listing where the Buy It Now option is available.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength> 19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.) </MaxLength>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BestOffer" type="ns:BestOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the status for a Best Offer. This container is
								only returned if applicable based on the listing and the value set for
								&lt;b&gt;Offer.Action&lt;/b&gt; field in the request. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier for an eBay order line item and
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. The &lt;b&gt;OrderLineItemID&lt;/b&gt; field is only
								returned if the &lt;b&gt;Offer.Action&lt;/b&gt; field is set to &lt;b&gt;Purchase&lt;/b&gt; in the input and
								the purchase is successful. A Purchase action in &lt;b&gt;PlaceOffer&lt;/b&gt; can be used
								for a fixed-price listing, or for an auction listing where the Buy It
								Now option is available.
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50 (Note: The eBay database specifies 38. ItemIDs and TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>PlaceOffer</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RelistFixedPriceItem -->
	<xs:element name="RelistFixedPriceItemRequest" type="ns:RelistFixedPriceItemRequestType"/>
	<xs:complexType name="RelistFixedPriceItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to take a single fixed-price item (or a single multi-item
				listing) that has ended and re-list it on a specified eBay site.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddFixedPriceItem, RelistItem, ReviseFixedPriceItem, GetCategories
				</RelatedCalls>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
				<SeeLink>
					<Title>Relisting Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=RelistingItems</URL>
				</SeeLink>
				<SeeLink>
					<Title>Relisting Your Item (eBay Web site onine help)</Title>
					<URL>http://pages.ebay.com/help/sell/relist.html</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ConsideringBestMatch</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BestMatchReviseRelist</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements hold the values for item properties that change for the
								relisted item. Item is a required input. At a minimum, the Item.ItemID
								property must be set to the ID of the original listing (a
								listing that ended in the past 90 days). By default, the new listing's
								Item object properties are the same as those of the original (ended)
								listing. By setting a new value in the Item object, the new listing
								uses the new value rather than the original value from the old
								listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedField" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the name of the field to delete from a listing.
								See the eBay Trading API guide for rules on deleting values when relisting items.
								Also see the relevant field descriptions to determine when to use DeletedField (and potential consequences).
								The request can contain zero, one, or many instances of DeletedField (one for each field to be deleted).
								DeletedField accepts the following path names, which delete the corresponding nodes:&lt;br&gt;
								&lt;br&gt;
								Some data (such as Variation nodes within Variations)
								can't be deleted by using DeletedFields. See the relevant field
								descriptions for how to delete such data.&lt;br&gt;
								&lt;br&gt;
								Item.ApplicationData&lt;br&gt;
								Item.AttributeSetArray&lt;br&gt;
								Item.Charity&lt;br&gt;
								Item.ConditionID&lt;br&gt;
								Item.ItemSpecifics&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.ProStoresStoreName&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.SellerThirdPartyUsername&lt;br&gt;
								Item.ListingDesigner.LayoutID&lt;br&gt;
								Item.ListingDesigner.ThemeID&lt;br&gt;
								Item.ListingDetails.LocalListingDistance&lt;br&gt;
								Item.ListingDetails.MinimumBestOfferMessage&lt;br&gt;
								Item.ListingDetails.MinimumBestOfferPrice&lt;br&gt;
								Item.ListingEnhancement[Value]&lt;br&gt;
								Item.PayPalEmailAddress&lt;br&gt;
								Item.PictureDetails.GalleryURL&lt;br&gt;
								Item.PictureDetails.PictureURL&lt;br&gt;
								Item.PostalCode&lt;br&gt;
								Item.ProductListingDetails&lt;br&gt;
								Item.SecondaryCategory&lt;br&gt;
								Item.SellerContactDetails&lt;br&gt;
								Item.SellerContactDetails.CompanyName&lt;br&gt;
								Item.SellerContactDetails.County&lt;br&gt;
								Item.SellerContactDetails.InternationalStreet&lt;br&gt;
								Item.SellerContactDetails.Phone2AreaOrCityCode&lt;br&gt;
								Item.SellerContactDetails.Phone2CountryCode&lt;br&gt;
								Item.SellerContactDetails.Phone2CountryPrefix&lt;br&gt;
								Item.SellerContactDetails.Phone2LocalNumber&lt;br&gt;
								Item.SellerContactDetails.PhoneAreaOrCityCode&lt;br&gt;
								Item.SellerContactDetails.PhoneCountryCode&lt;br&gt;
								Item.SellerContactDetails.PhoneCountryPrefix&lt;br&gt;
								Item.SellerContactDetails.PhoneLocalNumber&lt;br&gt;
								Item.SellerContactDetails.Street&lt;br&gt;
								Item.SellerContactDetails.Street2&lt;br&gt;
								Item.ShippingDetails.PaymentInstructions&lt;br&gt;
								Item.SKU&lt;br&gt;
								Item.SubTitle&lt;br&gt;
								These values are case-sensitive. Use values that match the case of the schema element names
								(Item.PictureDetails.GalleryURL) or make the initial letter of each field name lowercase (item.pictureDetails.galleryURL).
								However, do not change the case of letters in the middle of a field name.
								For example, item.picturedetails.galleryUrl is not allowed.&lt;br&gt;&lt;br&gt;
								To delete a listing enhancement like Featured, specify the value you are deleting;
								for example, Item.ListingEnhancement[Featured].
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RelistFixedPriceItem -->
	<xs:element name="RelistFixedPriceItemResponse" type="ns:RelistFixedPriceItemResponseType"/>
	<xs:complexType name="RelistFixedPriceItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the Item ID, SKU (if any), listing recommendations (if applicable), the
				estimated fees for the relisted item (except the Final Value Fee, which isn't calculated
				until the item has sold), the start and end times of the listing, and other details.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique item ID for the relisted item.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Item-level SKU for the new listing, if the seller specified
							Item.SKU in the listing. Variation SKUs are not returned
							(see GetItem instead).
						</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the relisted item.
								The fees do not include the Final Value Fee (FVF), which cannot
								be determined until an item is sold.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time the relisting became active on the eBay site.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time when the relisted item ends. This is the starting time plus
								the listing duration.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the primary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID passed in Item.PrimaryCategory was mapped to a new ID by eBay.
								If the primary category has not changed or it has expired with no replacement,
								CategoryID does not return a value.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the secondary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID passed in Item.SecondaryCategory was mapped to a new ID by eBay.
								If the secondary category has not changed or it has expired with no replacement,
								Category2ID does not return a value.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DiscountReason" type="ns:DiscountReasonCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The nature of the discount, if a discount applied.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSuggestions" type="ns:ProductSuggestionsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides a list of products recommended by eBay which match the item information
								provided by the seller.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingRecommendations" type="ns:ListingRecommendationsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of one or more &lt;b&gt;Recommendation&lt;/b&gt; containers. 
								Each &lt;b&gt;Recommendation&lt;/b&gt; container provides a message to the 
								seller on how a listing can be improved or brought up to standard in reqards to 
								Top-Rated Plus listing requirements, Item Specifics, picture requirements, and/or 
								a recommendation to use a product code to list the item, such as a UPC, an EAN, or 
								an ISBN. 
								&lt;br&gt;&lt;br&gt;
								This container is only returned if the &lt;b&gt;IncludeRecommendations&lt;/b&gt; 
								flag was included and set to 'true' in the &lt;b&gt;RelistFixedPriceItem&lt;/b&gt; request, and if 
								at least one listing recommendation exists for the newly relisted item. If
								one or more listing recommendations are returned, it will be at the seller's 
								discretion about whether to revise the item based on eBay's listing 
								recommendation(s).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RelistItem -->
	<xs:element name="RelistItemRequest" type="ns:RelistItemRequestType"/>
	<xs:complexType name="RelistItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to take a single item (or a single multi-item
				listing) and re-list it on a specified eBay site.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddItem, AddToItemDescription, GetItem, GetItemRecommendations,
					GetSellerList, RelistFixedPriceItem, ReviseItem
				</RelatedCalls>
				<SeeLink>
					<Title>Relisting Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=RelistingItems</URL>
				</SeeLink>
				<SeeLink>
					<URL>http://ebay.custhelp.com/cgi-bin/ebay.cfg/php/enduser/std_adp.php?p_faqid=1542</URL>
					<Title>Best practices for relisting items</Title>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ConsideringBestMatch</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BestMatchReviseRelist</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements hold the values for item properties that change for the
								item re-list. Item is a required input. At a minimum, the Item.ItemID
								property must be set to the ID of the listing being re-listed (a
								listing that ended in the past 90 days). By default, the new listing's
								Item object properties are the same as those of the original (ended)
								listing. By setting a new value in the Item object, the new listing
								uses the new value rather than the corresponding value from the old
								listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedField" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the name of the field to delete from a listing.
								See the eBay Web Services guide for rules on deleting values when relisting items.
								Also see the relevant field descriptions to determine when to use DeletedField (and potential consequences).
								The request can contain zero, one, or many instances of DeletedField (one for each field to be deleted).
								DeletedField accepts the following path names, which delete the corresponding nodes:&lt;br&gt;&lt;br&gt;
								Item.ApplicationData&lt;br&gt;
								Item.AttributeSetArray&lt;br&gt;
								Item.BuyItNowPrice&lt;br&gt;
								Item.Charity&lt;br&gt;
								Item.ConditionID&lt;br&gt;
								Item.ItemSpecifics&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.ProStoresStoreName&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.SellerThirdPartyUsername&lt;br&gt;
								Item.ListingDesigner.LayoutID&lt;br&gt;
								Item.ListingDesigner.ThemeID&lt;br&gt;
								Item.ListingDetails.LocalListingDistance&lt;br&gt;
								Item.ListingDetails.MinimumBestOfferMessage&lt;br&gt;
								Item.ListingDetails.MinimumBestOfferPrice&lt;br&gt;
								Item.ListingEnhancement[Value]&lt;br&gt;
								Item.PayPalEmailAddress&lt;br&gt;
								Item.PictureDetails.GalleryURL&lt;br&gt;
								Item.PictureDetails.PictureURL&lt;br&gt;
								Item.PostalCode&lt;br&gt;
								Item.ProductListingDetails&lt;br&gt;
								Item.SecondaryCategory&lt;br&gt;
								Item.SellerContactDetails&lt;br&gt;
								Item.SellerContactDetails.CompanyName&lt;br&gt;
								Item.SellerContactDetails.County&lt;br&gt;
								Item.SellerContactDetails.InternationalStreet&lt;br&gt;
								Item.SellerContactDetails.Phone2AreaOrCityCode&lt;br&gt;
								Item.SellerContactDetails.Phone2CountryCode&lt;br&gt;
								Item.SellerContactDetails.Phone2CountryPrefix&lt;br&gt;
								Item.SellerContactDetails.Phone2LocalNumber&lt;br&gt;
								Item.SellerContactDetails.PhoneAreaOrCityCode&lt;br&gt;
								Item.SellerContactDetails.PhoneCountryCode&lt;br&gt;
								Item.SellerContactDetails.PhoneCountryPrefix&lt;br&gt;
								Item.SellerContactDetails.PhoneLocalNumber&lt;br&gt;
								Item.SellerContactDetails.Street&lt;br&gt;
								Item.SellerContactDetails.Street2&lt;br&gt;
								Item.ShippingDetails.PaymentInstructions&lt;br&gt;
								Item.SKU&lt;br&gt;
								Item.SubTitle&lt;br&gt;
								These values are case-sensitive. Use values that match the case of the schema element names
								(Item.PictureDetails.GalleryURL) or make the initial letter of each field name lowercase (item.pictureDetails.galleryURL).
								However, do not change the case of letters in the middle of a field name.
								For example, item.picturedetails.galleryUrl is not allowed.&lt;br&gt;&lt;br&gt;
								To delete a listing enhancement like Featured, specify the value you are deleting;
								for example, Item.ListingEnhancement[Featured].
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RelistItem -->
	<xs:element name="RelistItemResponse" type="ns:RelistItemResponseType"/>
	<xs:complexType name="RelistItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the Item ID, SKU (if any), listing recommendations (if applicable), the
				estimated fees for the relisted item (except the Final Value Fee, which isn't calculated
				until the item has sold), the start and end times of the listing, and other details.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique item ID for the new listing.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the new item
								listing. The fees do not include the Final Value Fee (FVF), which cannot
								be determined until an item is sold.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time the new listing became active on the eBay site.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time when the new listing ends. This is the starting time plus
								the listing duration.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the primary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID passed in Item.PrimaryCategory was mapped to a new ID by eBay.
								If the primary category has not changed or it has expired with no replacement,
								CategoryID does not return a value.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the secondary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID passed in Item.SecondaryCategory was mapped to a new ID by eBay.
								If the secondary category has not changed or it has expired with no replacement,
								Category2ID does not return a value.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DiscountReason" type="ns:DiscountReasonCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The nature of the discount, if a discount applied.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSuggestions" type="ns:ProductSuggestionsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides a list of products recommended by eBay which match the item information
								provided by the seller.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingRecommendations" type="ns:ListingRecommendationsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of one or more &lt;b&gt;Recommendation&lt;/b&gt; containers. 
								Each &lt;b&gt;Recommendation&lt;/b&gt; container provides a message to the 
								seller on how a listing can be improved or brought up to standard in reqards to 
								Top-Rated Plus listing requirements, Item Specifics, picture requirements, and/or 
								a recommendation to use a product code to list the item, such as a UPC, an EAN, or 
								an ISBN.  
								&lt;br&gt;&lt;br&gt;
								This container is only returned if the &lt;b&gt;IncludeRecommendations&lt;/b&gt; 
								flag was included and set to 'true' in the &lt;b&gt;RelistItem&lt;/b&gt; request, and if 
								at least one listing recommendation exists for the newly relisted item. If
								one or more listing recommendations are returned, it will be at the seller's 
								discretion about whether to revise the item based on eBay's listing 
								recommendation(s).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RelistItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RemoveFromWatchList -->
	<xs:element name="RemoveFromWatchListRequest" type="ns:RemoveFromWatchListRequestType"/>
	<xs:complexType name="RemoveFromWatchListRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a user to remove one or more items from their My eBay watch list.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddToWatchList, GetMyeBayBuying, GetMyeBaySelling</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The ID of the item to be removed from the
								watch list. Either ItemID, RemoveAllItems, or VariationKey must
								be specified, but NOT more than one of these.
								Multiple ItemID fields can be specified in the same request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>RemoveFromWatchList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RemoveAllItems" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If true, then all the items in the user's
								watch list are removed. Either ItemID, RemoveAllItems, or VariationKey must be specified, but NOT more than one of these.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RemoveFromWatchList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VariationKey" type="ns:VariationKeyType" minOccurs="0" maxOccurs="unbounded">
					<xs:annotation>
							<xs:documentation>
								A variation (or set of variations) that you want to remove
								from the watch list. Either ItemID, RemoveAllItems, or VariationKey must be specified, but NOT more than one of these.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RemoveFromWatchList</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RemoveFromWatchList -->
	<xs:element name="RemoveFromWatchListResponse" type="ns:RemoveFromWatchListResponseType"/>
	<xs:complexType name="RemoveFromWatchListResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns information about the user's My eBay watch list.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="WatchListCount" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The current number of items in the user's watch list (after those
								specified in the call request have been removed)
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RemoveFromWatchList</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="WatchListMaximum" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The maximum number of items allowed in watch lists. Currently this value
								is 200, and is the same for all sites and all users.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RemoveFromWatchList</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RespondToBestOffer -->
	<xs:element name="RespondToBestOfferRequest" type="ns:RespondToBestOfferRequestType"/>
	<xs:complexType name="RespondToBestOfferRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables the seller of a Best Offer item to accept, decline, or counter offers
				made by bidders. Best offers can be declined in bulk, using the same message
				from the seller to the bidders of all rejected offers.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetBestOffers</RelatedCalls>
				<SeeLink>
					<Title>Enabling Best Offer</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EnablingBestOffer</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the item for which the BestOffer data is to be returned.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>RespondToBestOffer</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BestOfferID" type="ns:BestOfferIDType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The ID of a Best Offer for the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToBestOffer</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Action" type="ns:BestOfferActionCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The action taken on the Best Offer by the seller (e.g.,
								Accept, Decline, or Counter). Bulk Accept and Bulk
								Counter are not supported. That is, you cannot accept or
								counter multiple offers in a single call. You can,
								however, decline multiple offers in a single call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToBestOffer</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerResponse" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A comment from the seller to the buyer.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>250</MaxLength>
								<CallInfo>
									<CallName>RespondToBestOffer</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CounterOfferPrice" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The counter offer price. When Action is set to Counter,
								you must specify the amount for the counter offer with
								CounterOfferPrice. The value of CounterOfferPrice cannot
								exceed the Buy It Now price for a single quantity item.
								The value of CounterOfferPrice may exceed the Buy It Now
								price if the value for CounterOfferQuantity is greater
								than 1.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToBestOffer</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CounterOfferQuantity" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The quantity of items in the counter offer. When Action is set to
								Counter you must specify the quantity of items for the
								counter offer with CounterOfferQuantity.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToBestOffer</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RespondToBestOffer -->
	<xs:element name="RespondToBestOfferResponse" type="ns:RespondToBestOfferResponseType"/>
	<xs:complexType name="RespondToBestOfferResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains a list of BestOffers that were either accepted or declined.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="RespondToBestOffer" type="ns:BestOfferArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A list of BestOffers that were either accepted or declined.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToBestOffer</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RespondToFeedback -->
	<xs:element name="RespondToFeedbackRequest" type="ns:RespondToFeedbackRequestType"/>
	<xs:complexType name="RespondToFeedbackRequestType">
		<xs:annotation>
			<xs:documentation>
				Used to reply to feedback that has been left for a user, or to post a
				follow-up comment to a feedback comment the user has left for someone else.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetFeedback, LeaveFeedback</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="FeedbackID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for a Feedback record. Buying and selling partners
								leave feedback for one another after the completion of an order.
								Feedback is left at the order line item (transaction) level, so a
								Feedback comment for each line item in a Combined Payment order is
								expected from the buyer and seller. A unique &lt;b&gt;FeedbackID&lt;/b&gt; is created
								whenever a buyer leaves feedback for a seller, and vice versa. A
								&lt;b&gt;FeedbackID&lt;/b&gt; is created by eBay when feedback is left through the eBay
								site, or through the &lt;b&gt;LeaveFeedback&lt;/b&gt; call. &lt;b&gt;FeedbackIDs&lt;/b&gt; can be retrieved
								with the &lt;b&gt;GetFeedback&lt;/b&gt; call. In the &lt;b&gt;RespondToFeedback&lt;/b&gt; call, &lt;b&gt;FeedbackID&lt;/b&gt; can
								be used as an input filter to respond to a specific Feedback comment.
								Since Feedback is always linked to a unique order line item, an
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair or an &lt;b&gt;OrderLineItemID&lt;/b&gt; can also be used to
								respond to a Feedback comment.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToFeedback</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. A listing can have multiple
								order line items (transactions), but only one &lt;b&gt;ItemID&lt;/b&gt;. An &lt;b&gt;ItemID&lt;/b&gt; can be
								paired up with a corresponding &lt;b&gt;TransactionID&lt;/b&gt; and used as an input filter
								to respond to a Feedback comment in the &lt;b&gt;RespondToFeedback&lt;/b&gt; call. Unless
								the specific Feedback record is identified by a &lt;b&gt;FeedbackID&lt;/b&gt; or an
								&lt;b&gt;OrderLineItemID&lt;/b&gt; in the request, an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is
								required.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>RespondToFeedback</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay order line item (transaction). A
								&lt;b&gt;TransactionID&lt;/b&gt; can be paired up with its corresponding &lt;b&gt;ItemID&lt;/b&gt; and used as
								an input filter to respond to a Feedback comment in the
								&lt;b&gt;RespondToFeedback&lt;/b&gt; call. Unless the specific Feedback record is
								identified by a &lt;b&gt;FeedbackID&lt;/b&gt; or an &lt;b&gt;OrderLineItemID&lt;/b&gt; in the request, an
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is required.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>RespondToFeedback</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TargetUserID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The eBay user ID of the caller's order partner. The caller is either
								replyting to or following up on this user's Feedback comment.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToFeedback</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ResponseType" type="ns:FeedbackResponseCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether the response is a reply or a follow-up to a Feedback
								comment left by the user identified in the &lt;b&gt;TargetUserID&lt;/b&gt; field.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToFeedback</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ResponseText" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Textual comment that the user who is subject of feedback may leave in
								response or rebuttal to the Feedback comment. Alternatively, when the
								&lt;b&gt;ResponseType&lt;/b&gt; is &lt;b&gt;FollowUp&lt;/b&gt;, this value contains the text of the follow-up
								comment.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>80 (125 for the Taiwan site)</MaxLength>
								<CallInfo>
									<CallName>RespondToFeedback</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier for an eBay order line item and
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. Since Feedback is always linked to a
								unique order line item, an &lt;b&gt;OrderLineItemID&lt;/b&gt; can be used to respond
								to a Feedback comment.
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair or a &lt;b&gt;FeedbackID&lt;/b&gt; is used to identify
								a Feedback record, the &lt;b&gt;OrderLineItemID&lt;/b&gt; must be specified.
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50 (Note: ItemIDs and TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>RespondToFeedback</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RespondToFeedback -->
	<xs:element name="RespondToFeedbackResponse" type="ns:RespondToFeedbackResponseType"/>
	<xs:complexType name="RespondToFeedbackResponseType">
		<xs:annotation>
			<xs:documentation>
				Indicates the success or failure of the attempt to reply
				to feedback that has been left for a user, or to post a
				follow-up comment to a feedback comment a user has left
				for someone else.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RespondToWantItNowPost -->
	<xs:element name="RespondToWantItNowPostRequest" type="ns:RespondToWantItNowPostRequestType"/>
	<xs:complexType name="RespondToWantItNowPostRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to respond to a Want It Now post with an item listed on the eBay
				site. Responses appear on the Want It Now post page, with the item title, the
				price of the item, the number of bids on the item, and the time left before the
				listing ends. If the item has a picture, the picture is also included on the Want
				It Now post page.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					GetWantItNowSearchResults, GetWantItNowPost
				</RelatedCalls>
				<SeeLink>
					<Title>Want It Now</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=WantItNowChapter</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of an item listed on the eBay site.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>RespondToWantItNowPost</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PostID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of a Want It Now post on the eBay site.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RespondToWantItNowPost</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RespondToWantItNowPost -->
	<xs:element name="RespondToWantItNowPostResponse" type="ns:RespondToWantItNowPostResponseType"/>
	<xs:complexType name="RespondToWantItNowPostResponseType">
		<xs:annotation>
			<xs:documentation>
				Indicates the success or failure of the attempt to respond to a Want It Now post.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType" />
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseCheckoutStatus -->
	<xs:element name="ReviseCheckoutStatusRequest" type="ns:ReviseCheckoutStatusRequestType"/>
	<xs:complexType name="ReviseCheckoutStatusRequestType">
		<xs:annotation>
			<xs:documentation>
				A seller can use this call to update the payment details, the shipping details,
				and the status of an order.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>ReviseItem</RelatedCalls>
				<SeeLink>
					<Title>Checkout</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Checkout</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=WorkingWithCombinedPayment</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. A listing can have multiple
								order line items (transactions), but only one &lt;b&gt;ItemID&lt;/b&gt;. An &lt;b&gt;ItemID&lt;/b&gt; can be
								paired up with a corresponding &lt;b&gt;TransactionID&lt;/b&gt; and used as an input filter
								for &lt;b&gt;ReviseCheckoutStatus&lt;/b&gt;.
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;OrderLineItemID&lt;/b&gt; is used to identify a single line item order,
								or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line item
								(Combined Payment) order, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair must be
								specified. For a multiple line item (Combined Payment) order, &lt;b&gt;OrderID&lt;/b&gt;
								should be used. If &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; are specified, the
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is ignored if present in the same request.
								&lt;br /&gt;
								&lt;br /&gt;
								It is also possible to identify a single line item order with a
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;BuyerID&lt;/b&gt; combination, but this is not the most ideal
								approach since an error is returned if there are multiple
								order line items for that combination.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay order line item (transaction). An order
								line item is created once there is a commitment from a buyer to purchase
								an item. Since an auction listing can only have one order line item
								during the duration of the listing, the &lt;b&gt;TransactionID&lt;/b&gt; for
								auction listings is always 0. Along with its corresponding &lt;b&gt;ItemID&lt;/b&gt;, a
								&lt;b&gt;TransactionID&lt;/b&gt; is used and referenced during an order checkout flow and
								after checkout has been completed. The &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair can be
								used as an input filter for &lt;b&gt;ReviseCheckoutStatus&lt;/b&gt;.
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;OrderLineItemID&lt;/b&gt; is used to identify a single line item order,
								or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line item
								(Combined Payment) order, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair must be
								specified. For a multiple line item (Combined Payment) order, &lt;b&gt;OrderID&lt;/b&gt;
								must be used. If &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; are specified, the
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is ignored if present in the same request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier that identifies a single line item or multiple line
								item (Combined Payment) order.
								&lt;br&gt;&lt;br&gt;
								For a single line item order, the &lt;b&gt;OrderID&lt;/b&gt; value is identical to the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value that is generated upon creation of the order line
								item. For a Combined Payment order, the &lt;b&gt;OrderID&lt;/b&gt; value is created by eBay
								when the buyer or seller (sharing multiple, common order line items)
								combines multiple order line items into a Combined Payment order through
								the eBay site. A Combined Payment order can also be created by the
								seller through the &lt;b&gt;AddOrder&lt;/b&gt; call. The &lt;b&gt;OrderID&lt;/b&gt; can be used as an input
								filter for &lt;b&gt;ReviseCheckoutStatus&lt;/b&gt;.
								&lt;br&gt;&lt;br&gt;
								&lt;b&gt;OrderID&lt;/b&gt; overrides an &lt;b&gt;OrderLineItemID&lt;/b&gt; or &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair if
								these fields are also specified in the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AmountPaid" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The total amount paid by the buyer. For a motor vehicle purchased on eBay Motors,
								&lt;b&gt;AmountPaid&lt;/b&gt; is the total amount paid by the buyer for the deposit.
								&lt;b&gt;AmountPaid&lt;/b&gt; is optional if &lt;b&gt;CheckoutStatus&lt;/b&gt; is Incomplete and required if it
								is Complete.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaymentMethodUsed" type="ns:BuyerPaymentMethodCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Payment method used by the buyer. This field is required if &lt;b&gt;
								CheckoutStatus&lt;/b&gt; is Complete and the payment method is a trusted
								payment method other than PayPal. See eBay's
								&lt;a href="http://pages.ebay.com/help/policies/accepted-payments-policy.html"&gt;Accepted Payments Policy&lt;/a&gt;.
								If the payment method is PayPal, this field should not be used since only PayPal can set this field's
								value to "PayPal". ReviseCheckoutStatus cannot be used for a non-trusted
								payment method.
								&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								Required or allowed payment methods vary by site and category. Refer to
								&lt;a href="http://developer.ebay.com/DevZone/XML/docs/WebHelp/wwhelp/wwhimpl/js/html/wwhelp.htm?context=eBay_XML_API&amp;topic=PaymentMethodDifferences"&gt;
								Payment Method Differences (PaymentMethod)&lt;/a&gt; in the eBay
								Trading API Guide for information to help you determine which payment
								methods you are required or allowed to specify.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<AllValuesExcept>PayPal</AllValuesExcept>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CheckoutStatus" type="ns:CompleteStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The current checkout status of the order. Often, the seller or
								application will mark this value as 'Complete' if payment has been made. The &lt;b&gt;CheckoutStatus&lt;/b&gt;
								value cannot be updated by DE and AT sellers who are subject to the new payment
								process, and an attempt to do so in a &lt;b&gt;ReviseCheckoutStatus&lt;/b&gt; call
								will result in a call error.
								&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								The introduction of the new eBay payment process for the entire German and
								Austrian eBay marketplace has been delayed until further notice.&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingService" type="xs:token" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The shipping service selected by the buyer from among the shipping services
								offered by the seller (such as UPS Ground). For a list of valid values, call
								GeteBayDetails with DetailName set to ShippingServiceDetails. The
								ShippingServiceDetails.ValidForSellingFlow flag must also be present.
								Otherwise, that particular shipping service option is no longer valid and
								cannot be offered to buyers through a listing.
								&lt;br/&gt;&lt;br/&gt;
								&lt;span class="tablenote"&gt;
								&lt;strong&gt;Note:&lt;/strong&gt; &lt;strong&gt;ReviseCheckoutStatus&lt;/strong&gt; is not available for the Global Shipping program; specifying InternationalPriorityShipping as a value for this field will produce an error.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<ListBasedOn>ShippingServiceCodeType</ListBasedOn>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingIncludedInTax" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An indicator of whether shipping costs were included in the
								taxable amount. .
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<Default>false</Default>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CheckoutMethod" type="ns:CheckoutMethodCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								<!-- This field is no longer supported and will be ignored if included in the 
								request. -->
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
								<!-- <CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo> -->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="InsuranceType" type="ns:InsuranceSelectedCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Enumeration value that indicates whether shipping insurance was offered to and
								selected by the buyer.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaymentStatus" type="ns:RCSPaymentStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Marks the order as paid or awaiting payment in My eBay. If you specify
								Paid, My eBay displays an icon for each item in the order to indicate
								that the order status is Paid. If you specify Pending, this indicates
								that the order is awaiting payment. (Some applications may use Pending
								when the buyer has paid but the funds have not yet been sent to the
								seller's financial institution.)
								&lt;br&gt;
								&lt;br&gt;
								&lt;b&gt;ReviseCheckoutStatus&lt;/b&gt; cannot be used to update payment and checkout
								status for a non-trusted payment method. See eBay's &lt;a href="
								http://pages.ebay.com/help/policies/accepted-payments-policy.html"&gt;
								Accepted Payments Policy&lt;/a&gt; for more information on trusted
								payment methods. If the payment method is PayPal, this field should not
								be used since PayPal automatically set this field's value to "Paid" upon
								receiving the buyer's payment.
								&lt;br&gt;
								&lt;br&gt;
								The &lt;b&gt;PaymentStatus&lt;/b&gt; value cannot be updated by DE and AT sellers
								who are subject to the new eBay payment process, and an attempt to do so in a
								&lt;b&gt;ReviseCheckoutStatus&lt;/b&gt; call will result in a call error.
								&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								The introduction of the new eBay payment process for the entire German and
								Austrian eBay marketplace has been delayed until further notice.&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
									<OnlyTheseValues>Paid, Pending</OnlyTheseValues>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AdjustmentAmount" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Discount or charge agreed to by the buyer and seller. A positive value
								indicates that the amount is an extra charge being paid to the seller by
								the buyer. A negative value indicates that the amount is a discount given
								to the buyer by the seller.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingAddress" type="ns:AddressType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							  For internal use.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="BuyerID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								eBay user ID for the order's buyer. A single line item order can
								actually be identified by a &lt;b&gt;BuyerID&lt;/b&gt;/&lt;b&gt;ItemID&lt;/b&gt; pair, but this approach is
								not recommended since an error is returned if there are multiple
								order line items for that combination. &lt;b&gt;BuyerID&lt;/b&gt; is ignored if any other valid
								filter or filter combination is used in the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingInsuranceCost" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The amount of money paid for shipping insurance.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SalesTax" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The sales tax amount for the order. This field should be used if sales tax
								was applied to the order.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingCost" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The amount of money paid for shipping.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EncryptedID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Not supported.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>20</MaxLength>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExternalTransaction" type="ns:ExternalTransactionType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of a unique identifier and timestamp for the electronic
								payment of an order. An &lt;b&gt;ExternalTransactionID&lt;/b&gt; is not exposed
								to a new DE or AT seller who is subject to the new eBay payment process.
								&lt;br&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								The introduction of the new eBay payment process for the entire German and
								Austrian eBay marketplace has been delayed until further notice.&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="MultipleSellerPaymentID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Not supported.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CODCost" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This dollar value indicates the money due from the buyer upon delivery of the item.
								&lt;br&gt;&lt;br&gt;
								This field should only be specified in the &lt;b&gt;ReviseCheckoutStatus&lt;/b&gt;
								request if 'COD' (cash-on-delivery) was the payment method selected by the buyer
								and it is included as the &lt;b&gt;PaymentMethodUsed&lt;/b&gt; value in the same
								request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>Other Shipping Features</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CODInShippingDetails</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier for an eBay order line item and
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. For a single line item order, the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value can be passed into the &lt;b&gt;OrderID&lt;/b&gt; field to revise the
								checkout status of the order.
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is used to identify a single line
								item order, or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line
								item (Combined Payment) order, the &lt;b&gt;OrderLineItemID&lt;/b&gt; must be specified.
								For a multiple line item (Combined Payment) order, &lt;b&gt;OrderID&lt;/b&gt; should be
								used. If &lt;b&gt;OrderLineItemID&lt;/b&gt; is specified, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair are
								ignored if present in the same request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>100</MaxLength>
								<CallInfo>
									<CallName>ReviseCheckoutStatus</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseCheckoutStatus -->
	<xs:element name="ReviseCheckoutStatusResponse" type="ns:ReviseCheckoutStatusResponseType"/>
	<xs:complexType name="ReviseCheckoutStatusResponseType">
		<xs:annotation>
			<xs:documentation>
      	Indicates success or failure of the attempt to revise the listing's checkout status.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseFixedPriceItem -->
	<xs:element name="ReviseFixedPriceItemRequest" type="ns:ReviseFixedPriceItemRequestType"/>
	<xs:complexType name="ReviseFixedPriceItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to change the properties of a currently active
				fixed-price listing (including multi-variation listings).
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddFixedPriceItem, RelistFixedPriceItem, ReviseItem</RelatedCalls>
				<SeeLink>
					<Title>Revising Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=RevisingItems</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ConsideringBestMatch</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BestMatchReviseRelist</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements hold the values for item details that you want to change.
								The Item.ItemID must always be set to the ID of the listing being changed.
								Only specify Item fields for the details that are changing. Unless
								otherwise specified in the field descriptions below, the listing retains
								its existing values for fields that you don't pass in the
								ReviseFixedPriceItem request. Use DeletedField to remove a field from the
								listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedField" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the name of a field to delete from a listing. The request can
								contain zero, one, or many instances of DeletedField (one for each field
								to be deleted). See the relevant field descriptions to determine when to
								use DeletedField (and potential consequences).
								&lt;br&gt;&lt;br&gt;
								You cannot delete required fields from a listing.
								&lt;br&gt;&lt;br&gt;
								Some fields are optional when you first list an item (e.g.,
								SecondaryCategory), but once they are set they cannot be deleted when you
								revise an item. Some optional fields cannot be deleted if the item has
								bids and/or ends within 12 hours. Some optional fields cannot be deleted
								if other fields depend on them. See the eBay Trading API guide for rules
								on removing values when revising items.
								&lt;br&gt;&lt;br&gt;
								Some data (such as Variation nodes within Variations) can't be deleted by
								using DeletedFields. See the relevant field descriptions for how to delete
								such data.
								&lt;br&gt;&lt;br&gt;
								DeletedField accepts the following path names, which delete the
								corresponding nodes:
								&lt;br&gt;&lt;br&gt;
								Item.ApplicationData&lt;br&gt;
								Item.AttributeSetArray&lt;br&gt;
								Item.ConditionID&lt;br&gt;
								Item.ItemSpecifics&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.ProStoresStoreName&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.SellerThirdPartyUsername&lt;br&gt;
								Item.ListingDesigner.LayoutID&lt;br&gt;
								Item.ListingDesigner.ThemeID&lt;br&gt;
								Item.ListingEnhancement[Value]&lt;br&gt;
								Item.PayPalEmailAddress&lt;br&gt;
								Item.PictureDetails.GalleryURL&lt;br&gt;
								Item.PictureDetails.PictureURL&lt;br&gt;
								Item.PostalCode&lt;br&gt;
								Item.ProductListingDetails&lt;br&gt;
								Item.SellerContactDetails&lt;br&gt;
								Item.SellerContactDetails.CompanyName&lt;br&gt;
								Item.SellerContactDetails.County&lt;br&gt;
								Item.SellerContactDetails.InternationalStreet&lt;br&gt;
								Item.SellerContactDetails.Phone2AreaOrCityCode&lt;br&gt;
								Item.SellerContactDetails.Phone2CountryCode&lt;br&gt;
								Item.SellerContactDetails.Phone2CountryPrefix&lt;br&gt;
								Item.SellerContactDetails.Phone2LocalNumber&lt;br&gt;
								Item.SellerContactDetails.PhoneAreaOrCityCode&lt;br&gt;
								Item.SellerContactDetails.PhoneCountryCode&lt;br&gt;
								Item.SellerContactDetails.PhoneCountryPrefix&lt;br&gt;
								Item.SellerContactDetails.PhoneLocalNumber&lt;br&gt;
								Item.SellerContactDetails.Street&lt;br&gt;
								Item.SellerContactDetails.Street2&lt;br&gt;
								Item.ShippingDetails.PaymentInstructions&lt;br&gt;
								Item.SKU (unless InventoryTrackingMethod is SKU)&lt;br&gt;
								Item.SubTitle
								&lt;br&gt;&lt;br&gt;
								These values are case-sensitive. Use values that match the case of the
								schema element names (Item.PictureDetails.GalleryURL) or make the initial
								letter of each field name lowercase (item.pictureDetails.galleryURL).
								However, do not change the case of letters in the middle of a field name.
								For example, item.picturedetails.galleryUrl is not allowed.
								&lt;br&gt;&lt;br&gt;
								To delete a listing enhancement like BoldTitle, specify the value you are
								deleting in square brackets ("[ ]"); for example,
								Item.ListingEnhancement[BoldTitle].
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseFixedPriceItem -->
	<xs:element name="ReviseFixedPriceItemResponse" type="ns:ReviseFixedPriceItemResponseType"/>
	<xs:complexType name="ReviseFixedPriceItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the Item ID, SKU (if any), listing recommendations (if applicable), the
				estimated fees for the revised listing (except the Final Value Fee, which isn't calculated
				until the item has sold), the start and end times of the listing, and other details.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Item ID that uniquely identifies the item listing that was revised.
								Provided for confirmation purposes. The value returned should be the
								same as the item ID specified in the ItemID property of the Item object
								specified as input for the call.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Item-level SKU for the listing, if the seller specified
								Item.SKU for the listing. Variation SKUs are not returned
								(see GetItem instead).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Starting date and time for the listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time when the new listing ends. This equals the starting time
								plus the listing duration.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the revised item
								listing. The fees do not include the Final Value Fee (FVF), which cannot
								be determined until an item is sold. Revising an item does not itself
								incur a fee. However, certain item properties are fee-based and result
								in the return of fees in the call's response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>eBay.com Fees</Title>
									<URL>http://pages.ebay.com/help/sell/fees.html</URL>
								</SeeLink>
								<SeeLink>
									<Title>Fees per Site</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeesPerSite</URL>
								</SeeLink>
								<SeeLink>
									<Title>Final Value Fees and Credits</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FinalValueFeesAndCredits</URL>
								</SeeLink>
								<SeeLink>
									<Title>Final Value Fees</Title>
									<URL>http://pages.ebay.com/help/sell/fvf.html</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the primary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID passed in Item.PrimaryCategory was mapped to a new ID by eBay.
								If the primary category has not changed or it has expired with no replacement,
								CategoryID does not return a value.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the secondary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID passed in Item.SecondaryCategory was mapped to a new ID by eBay.
								If the secondary category has not changed or it has expired with no replacement,
								Category2ID does not return a value.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DiscountReason" type="ns:DiscountReasonCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The nature of the discount, if a discount applied.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSuggestions" type="ns:ProductSuggestionsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides a list of products recommended by eBay which match the item information
								provided by the seller.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingRecommendations" type="ns:ListingRecommendationsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of one or more &lt;b&gt;Recommendation&lt;/b&gt; containers. 
								Each &lt;b&gt;Recommendation&lt;/b&gt; container provides a message to the 
								seller on how a listing can be improved or brought up to standard in reqards to 
								Top-Rated Plus listing requirements, Item Specifics, picture requirements, and/or 
								a recommendation to use a product code to list the item, such as a UPC, an EAN, or 
								an ISBN. 
								&lt;br&gt;&lt;br&gt;
								This container is only returned if the &lt;b&gt;IncludeRecommendations&lt;/b&gt; 
								flag was included and set to 'true' in the &lt;b&gt;ReviseFixedPriceItem&lt;/b&gt; request, and if 
								at least one listing recommendation exists for the listing about to be revised. If
								one or more listing recommendations are returned, it will be at the seller's 
								discretion about whether to revise the item again based on eBay's listing 
								recommendation(s).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseInventoryStatus -->
	<xs:element name="ReviseInventoryStatusRequest" type="ns:ReviseInventoryStatusRequestType"/>
	<xs:complexType name="ReviseInventoryStatusRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to change the price and quantity of a currently-
				active, fixed-price listing. Using ReviseInventoryStatus to modify
				data qualifies as revising the listing.
				&lt;br&gt;
				&lt;br&gt;
				Inputs are the item IDs or SKUs of the listings being revised,
				and the price and quantity that are
				being changed for each revision. Only applicable to fixed-price listings.&lt;br&gt;
				&lt;br&gt;
				Changing the price or quantity of a currently-
				active, fixed-price listing does not reset the Best Match performance score.
				For Best Match information related to multi-variation listings, see the Best
				Match information at the following topic:
				&lt;a href="http://pages.ebay.com/sell/variation/"&gt;Multi-quantity Fixed Price
				listings with variations&lt;/a&gt;.&lt;br&gt;
				&lt;br&gt;
				As with all listing calls, the site you specify in the request URL
				(for SOAP) or the X-EBAY-API-SITEID HTTP header (for XML)
				should match the original listing's &lt;b&gt;Item.Site&lt;/b&gt; value.
				In particular, this is a best practice when you submit new and
				revised listings.&lt;br&gt;
				&lt;br&gt;
				&lt;b&gt;For Large Merchant Services users:&lt;/b&gt; When you use ReviseInventoryStatus within a Merchant Data file,
				it must be enclosed within two BulkDataExchangeRequest tags.
				After release 637, a namespace is returned in the BulkDataExchangeResponseType
				(top level) of the response. The BulkDataExchange tags are not shown in the call input/output descriptions.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Enables a seller to change the price and quantity of currently active fixed-price items.
				</Summary>
				<RelatedCalls>
					AddItems, GetSellerList, ReviseItem, RelistItem
				</RelatedCalls>
				<SeeLink>
					<Title>Standard Data for All Calls</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=TargetSite</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ConsideringBestMatch</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BestMatchReviseRelist</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="InventoryStatus" type="ns:InventoryStatusType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Contains the updated quantity and/or price of a listing
								being revised. You should not modify the same listing twice
								(by using a duplicate ItemID or SKU) in the same request;
								otherwise, you may get an error or unexpected results.
								(For example, you should not use one InventoryStatus node to
								update the quantity and another InventoryStatus node to update
								the price of the same item.) You can pass up to 4 InventoryStatus nodes in a single request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseInventoryStatus</CallName>
									<RequiredInput>Yes</RequiredInput>
									<MaxOccurs>4</MaxOccurs>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseInventoryStatus -->
	<xs:element name="ReviseInventoryStatusResponse" type="ns:ReviseInventoryStatusResponseType"/>
	<xs:complexType name="ReviseInventoryStatusResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the Item ID or SKU with changed Price and Quantity for the revised listing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="InventoryStatus" type="ns:InventoryStatusType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Confirms the quantity and price associated with a listing 
								or variation that was revised.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<allValuesExcept>StartTime, EndTime</allValuesExcept>
									<CallName>ReviseInventoryStatus</CallName>
									<Returned>Always</Returned>
									<MaxOccurs>4</MaxOccurs>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:InventoryFeesType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for a 
								listing that was revised. Use the ItemID to correlate the 
								Fees data with the InventoryStatus data in the response. 
								The fees do not include the Final Value Fee (FVF), 
								which can't be determined until the listing has sales.&lt;br&gt;
								&lt;br&gt;
								If you revise a variation in a multi-variation listing, 
								the fees are for the entire listing. The insertion fee and
								listing fee are affected by the highest priced variation 
								in the listing (which is not necessarily the variation that
								you passed in the request).&lt;br&gt;
								&lt;br&gt;
								Also note that the call returns only one Fees node per listing.
								For example, if you revise 4 variations from the same 
								multi-variation listing, the response includes 4 
								InventoryStatus nodes and 1 Fees node.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseInventoryStatus</CallName>
									<Returned>Always</Returned>
								</CallInfo>
								<SeeLink>
									<Title>eBay.com Fees</Title>
									<URL>http://pages.ebay.com/help/sell/fees.html</URL>
								</SeeLink>
								<SeeLink>
									<Title>Fees per Site</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FeesPerSite</URL>
								</SeeLink>
								<SeeLink>
									<Title>Final Value Fees and Credits</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=FinalValueFeesAndCredits</URL>
								</SeeLink>
								<SeeLink>
									<Title>Final Value Fees</Title>
									<URL>http://pages.ebay.com/help/sell/fvf.html</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseItem -->
	<xs:element name="ReviseItemRequest" type="ns:ReviseItemRequestType"/>
	<xs:complexType name="ReviseItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to change the properties of a currently active listing.&amp;nbsp;&lt;b&gt;Also for Half.com&lt;/b&gt;.
				&lt;br&gt;
				&lt;br&gt;
				After one item in a multi-quantity fixed-price listing has been sold, you can not
				the values in the Title, Primary Category, Secondary Category, Listing Duration,
				and Listing Type fields for that listing. However, all other fields in the
				multi-quantity, fixed-price listing are editable.
				&lt;br&gt;
				&lt;br&gt;
				Inputs are the Item ID of the listing you are revising, and the field or fields
				that you are updating.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddItem, AddToItemDescription, GetItem, GetSellerList,
					RelistItem, ReviseFixedPriceItem, GetCategories, GetCategoryMappings
				</RelatedCalls>
				<SeeLink>
					<Title>Revising Items</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=RevisingItems</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ConsideringBestMatch</URL>
				</SeeLink>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=BestMatchReviseRelist</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements hold the values for properties that are changing. The
								Item.ItemID property must always be set to the ID of the item listing being
								changed. Set values in the Item object only for those properties that are
								changing. Use DeletedField to remove a property.
								&lt;br&gt;&lt;br&gt;
								Applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedField" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the name of a field to delete from a listing. See the eBay
								Trading API guide for rules on deleting values when revising items. Also
								see the relevant field descriptions to determine when to use DeletedField
								(and potential consequences). The request can contain zero, one, or many
								instances of DeletedField (one for each field to be deleted).
								&lt;br&gt;&lt;br&gt;
								You cannot delete required fields from a listing.
								&lt;br&gt;&lt;br&gt;
								Some fields are optional when you first list an item (e.g.,
								SecondaryCategory), but once they are set they cannot be deleted when you
								revise an item. Some optional fields cannot be deleted from auction
								listings if the item has bids and/or ends within 12 hours. Some optional
								fields cannot be deleted if other fields depend on them.
								&lt;br&gt;&lt;br&gt;
								Some data (such as Variation nodes within Variations) can't be deleted by
								using DeletedFields. See the relevant field descriptions for how to delete
								such data. See the eBay Web Services guide for rules on removing values
								when revising items. Also see the relevant field descriptions for details
								on when to use DeletedField (and potential consequences).
								&lt;br&gt;&lt;br&gt;
								DeletedField accepts the following path names, which delete the
								corresponding nodes:
								&lt;br&gt;&lt;br&gt;
								Item.ApplicationData&lt;br&gt;
								Item.AttributeSetArray&lt;br&gt;
								Item.BuyItNowPrice&lt;br&gt;
								Item.ConditionID&lt;br&gt;
								Item.ExtendedSellerContactDetails&lt;br&gt;
								Item.ClassifiedAdContactByEmailEnabled&lt;br&gt;
								Item.ItemSpecifics&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.ProStoresStoreName&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.SellerThirdPartyUsername&lt;br&gt;
								Item.ListingDesigner.LayoutID&lt;br&gt;
								Item.ListingDesigner.ThemeID&lt;br&gt;
								Item.ListingDetails.MinimumBestOfferMessage&lt;br&gt;
								Item.ListingDetails.MinimumBestOfferPrice&lt;br&gt;
								Item.ListingEnhancement[Value]&lt;br&gt;
								Item.PayPalEmailAddress&lt;br&gt;
								Item.PictureDetails.GalleryURL&lt;br&gt;
								Item.PictureDetails.PictureURL&lt;br&gt;
								Item.PostalCode&lt;br&gt;
								Item.ProductListingDetails&lt;br&gt;
								Item.SellerContactDetails&lt;br&gt;
								Item.SellerContactDetails.CompanyName&lt;br&gt;
								Item.SellerContactDetails.County&lt;br&gt;
								Item.SellerContactDetails.InternationalStreet&lt;br&gt;
								Item.SellerContactDetails.Phone2AreaOrCityCode&lt;br&gt;
								Item.SellerContactDetails.Phone2CountryCode&lt;br&gt;
								Item.SellerContactDetails.Phone2CountryPrefix&lt;br&gt;
								Item.SellerContactDetails.Phone2LocalNumber&lt;br&gt;
								Item.SellerContactDetails.PhoneAreaOrCityCode&lt;br&gt;
								Item.SellerContactDetails.PhoneCountryCode&lt;br&gt;
								Item.SellerContactDetails.PhoneCountryPrefix&lt;br&gt;
								Item.SellerContactDetails.PhoneLocalNumber&lt;br&gt;
								Item.SellerContactDetails.Street&lt;br&gt;
								Item.SellerContactDetails.Street2&lt;br&gt;
								Item.ShippingDetails.PaymentInstructions&lt;br&gt;
								Item.SKU (unless InventoryTrackingMethod is SKU)&lt;br&gt;
								Item.SubTitle
								&lt;br&gt;&lt;br&gt;
								These values are case-sensitive. Use values that match the case of the
								schema element names (Item.PictureDetails.GalleryURL) or make the initial
								letter of each field name lowercase (item.pictureDetails.galleryURL).
								However, do not change the case of letters in the middle of a field name.
								For example, item.picturedetails.galleryUrl is not allowed.
								&lt;br&gt;&lt;br&gt;
								To delete a listing enhancement like BoldTitle, specify the value you are
								deleting in square brackets ("[ ]"); for example,
								Item.ListingEnhancement[BoldTitle].
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VerifyOnly" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							<!--
							Supporting VerifyOnly for ReviseItem call as part of project 24083 (API - Critical enhancements).
							-->
							When the VerifyOnly boolean tag value is supplied as 'true', the response will include the calculated
							listing price change if there is an increase in the BIN/Start price, but does not persist the values in DB.
							This call is similar to VerifyAddItem in revise mode.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseItem -->
	<xs:element name="ReviseItemResponse" type="ns:ReviseItemResponseType"/>
	<xs:complexType name="ReviseItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the Item ID, SKU (if any), listing recommendations (if applicable), the
				estimated fees for the revised listing (except the Final Value Fee, which isn't calculated
				until the item has sold), the start and end times of the listing, and other details.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Item ID that uniquely identifies the item listing that was revised.
								Provided for confirmation purposes. The value returned should be the
								same as the item ID specified in the ItemID property of the Item object
								specified as input for the call.
								Also applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StartTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Starting date and time for the revised listing.
								Also returned for Half.com (for Half.com, the start time is
								always the time the item was originally listed).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndTime" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Date and time when the new listing ends. This is the starting time
								plus the listing duration.
								Also returned for Half.com, but for Half.com the actual end time is GTC
								(not the end time returned in the response).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the revised item
								listing. The fees do not include the Final Value Fee (FVF), which cannot
								be determined until an item is sold. Revising an item does not itself
								incur a fee. However, certain item properties are fee-based and result
								in the return of fees in the call's response.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the primary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID passed in Item.PrimaryCategory was mapped to a new ID by eBay.
								If the primary category has not changed or it has expired with no replacement,
								CategoryID does not return a value.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the secondary category in which the item was listed.
								Only returned if you set Item.CategoryMappingAllowed to true in the request
								and the ID passed in Item.SecondaryCategory was mapped to a new ID by eBay.
								If the secondary category has not changed or it has expired with no replacement,
								Category2ID does not return a value.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>10</MaxLength>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VerifyOnly" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
							Supporting VerifyOnly for ReviseItem call as part of project 24083 (API - Critical enhancements).
							When the VerifyOnly boolean tag value is supplied as 'true', the response will include the calculated
							listing price change if there is an increase in the BIN/Start price, but does not persist the values in DB.
							This call is simialr to VerifyAddItem in revise mode.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DiscountReason" type="ns:DiscountReasonCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								The nature of the discount, if a discount applied.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductSuggestions" type="ns:ProductSuggestionsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Provides a list of products recommended by eBay which match the item information
								provided by the seller.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ListingRecommendations" type="ns:ListingRecommendationsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of one or more &lt;b&gt;Recommendation&lt;/b&gt; containers. 
								Each &lt;b&gt;Recommendation&lt;/b&gt; container provides a message to the 
								seller on how a listing can be improved or brought up to standard in reqards to 
								Top-Rated Plus listing requirements, Item Specifics, picture requirements, and/or 
								a recommendation to use a product code to list the item, such as a UPC, an EAN, or 
								an ISBN.  
								&lt;br&gt;&lt;br&gt;
								This container is only returned if the &lt;b&gt;IncludeRecommendations&lt;/b&gt; 
								flag was included and set to 'true' in the &lt;b&gt;ReviseItem&lt;/b&gt; request, and if 
								at least one listing recommendation exists for the listing about to be revised. If
								one or more listing recommendations are returned, it will be at the seller's 
								discretion about whether to revise the item again based on eBay's listing 
								recommendation(s).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseMyMessages -->
	<xs:element name="ReviseMyMessagesRequest" type="ns:ReviseMyMessagesRequestType"/>
	<xs:complexType name="ReviseMyMessagesRequestType">
		<xs:annotation>
			<xs:documentation>
				Sets the read state for messages, sets the flagged state of messages,
				and moves messages into and out of folders.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddMemberMessagesAAQToBidder, DeleteMyMessages, GetMessagePreferences,
					GetMemberMessages, GetMyMessages, ReviseMyMessagesFolders
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="MessageIDs" type="ns:MyMessagesMessageIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains a list of up to 10 MessageID values.
								&lt;br&gt;&lt;br&gt;
								MessageIDs must be included in
								the request. Messages in the Sent box cannot be moved,
								marked as Read, or Flagged.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseMyMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AlertIDs" type="ns:MyMessagesAlertIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field will be deprecated in an upcoming release.
								This field formerly contained a list of up to 10 AlertID values.
								&lt;br&gt;&lt;br&gt;
								Alerts cannot be flagged. Alerts cannot be
								moved into a new folder until they have been resolved.
								&lt;br&gt;&lt;br&gt;
								Resolve alerts by marking Read (if no action is
								required), or by using ActionURL (if action is
								required).
							</xs:documentation>
							<xs:appinfo>
								<NoCalls/>
				<!-- <CallInfo>
									<CallName>ReviseMyMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo> -->
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Read" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Changes the read states of all
								messages specified in a request.
								At least one of the following
								must be specified in the
								request: Read, Flagged, or FolderID.
								Messages in the Sent box cannot be moved,
								marked as Read, or Flagged.
								&lt;br&gt;&lt;br&gt;
								Note that messages retrieved
								with the API are not automatically marked Read,
								and must be marked Read with this call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseMyMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Flagged" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Changes the flagged states of all messages specified in
								a request by their MessageID values. At least one of
								Read, Flagged, or FolderID must be specified in the
								request. Messages in the Sent box cannot be moved,
								marked as Read, or Flagged.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseMyMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FolderID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An ID that uniquely identifies the My Messages folder to
								move messages into. At least one of Read,
								Flagged, or FolderID must be specified in the request.
								&lt;br&gt;&lt;br&gt;
								Messages
								in the Sent box cannot be moved, marked as Read, or
								Flagged.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseMyMessages</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseMyMessages -->
	<xs:element name="ReviseMyMessagesResponse" type="ns:ReviseMyMessagesResponseType"/>
	<xs:complexType name="ReviseMyMessagesResponseType">
		<xs:annotation>
			<xs:documentation>
				The response to ReviseMyMessagesRequestType. If the request was successful, 
				ReviseMyMessages returns nothing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseMyMessagesFolders -->
	<xs:element name="ReviseMyMessagesFoldersRequest" type="ns:ReviseMyMessagesFoldersRequestType"/>
	<xs:complexType name="ReviseMyMessagesFoldersRequestType">
		<xs:annotation>
			<xs:documentation>
				Renames, removes, or restores the specified My Messages folders for
				a given user.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddMemberMessagesAAQToBidder, DeleteMyMessages, GetMessagePreferences,
					GetMemberMessages, GetMyMessages, ReviseMyMessages
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Operation" type="ns:MyMessagesFolderOperationCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates the type of operation to perform on a
								specified My Messages folder. Operations include creating,
								renaming, removing, and restoring folders. Operations
								cannot be performed on the Inbox and Sent folders.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseMyMessagesFolders</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FolderID" type="xs:long" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								An ID that uniquely identifies the My Messages
								folder to perform the operation on. This value is set by
								eBay and cannot be changed. Retrieve FolderIDs
								by calling GetMyMessages with a DetailLevel of
								ReturnSummary. Inbox is FolderID = 0, and Sent is
								FolderID = 1.
								</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseMyMessagesFolders</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FolderName" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
							The name of a specified My Messages folder. Depending
							on the specified Operation, the value is an existing
							folder name or a new folder name. Retrieve existing
							FolderNames by calling GetMyMessages with a DetailLevel
							of ReturnSummary. Inbox is FolderID = 0, and Sent is
							FolderID = 1.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseMyMessagesFolders</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseMyMessagesFolders -->
	<xs:element name="ReviseMyMessagesFoldersResponse" type="ns:ReviseMyMessagesFoldersResponseType"/>
	<xs:complexType name="ReviseMyMessagesFoldersResponseType">
		<xs:complexContent>
		<xs:annotation>
			<xs:documentation>
				The response to ReviseMyMessagesFoldersRequestType. If the request was successful, 
				ReviseMyMessagesFolders returns nothing.
			</xs:documentation>
		</xs:annotation>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseSellingManagerInventoryFolder -->
	<xs:element name="ReviseSellingManagerInventoryFolderRequest" type="ns:ReviseSellingManagerInventoryFolderRequestType"/>
	<xs:complexType name="ReviseSellingManagerInventoryFolderRequestType">
		<xs:annotation>
			<xs:documentation>
			  Renames a Selling Manager inventory folder.
				This call is subject to change without notice; the deprecation process is
				inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Revises the name of a Selling Manager inventory folder.
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Folder" type="ns:SellingManagerFolderDetailsType" minOccurs="0" >
						<xs:annotation>
							<xs:documentation>
								Identifier of the folder to be modified. Valid inputs are folder ID,
								folder name, and comments.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerInventoryFolder</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseSellingManagerInventoryFolder -->
	<xs:element name="ReviseSellingManagerInventoryFolderResponse" type="ns:ReviseSellingManagerInventoryFolderResponseType"/>
	<xs:complexType name="ReviseSellingManagerInventoryFolderResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of a revise folder operation.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Folder" type="ns:SellingManagerFolderDetailsType" minOccurs="0" >
						<xs:annotation>
							<xs:documentation>
								Contains information about the folder that has been renamed.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerInventoryFolder</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseSellingManagerProduct -->
	<xs:element name="ReviseSellingManagerProductRequest" type="ns:ReviseSellingManagerProductRequestType"/>
	<xs:complexType name="ReviseSellingManagerProductRequestType">
		<xs:annotation>
			<xs:documentation>
				Revises a Selling Manager product.
				&lt;br&gt;&lt;br&gt;
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SellingManagerProductDetails" type="ns:SellingManagerProductDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The details of the product that is being revised.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerProduct</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingManagerFolderDetails" type="ns:SellingManagerFolderDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The details of the folder for this product.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerProduct</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedField" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the name of a field to remove from a Selling Manager product.
								The request can contain zero, one, or many instances of DeletedField (one for each field to be removed).
								DeletedField accepts the following path names, which remove the corresponding fields:&lt;br&gt;&lt;br&gt;
								SellingManagerProductDetails.CustomLabel&lt;br&gt;
								SellingManagerProductDetails.QuantityAvailable&lt;br&gt;
								SellingManagerProductDetails.UnitCost&lt;br&gt;
								These values are case-sensitive. Use values that match the case of the schema element names.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerProduct</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingManagerProductSpecifics" type="ns:SellingManagerProductSpecificsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies an eBay category associated with the product,
								defines Item Specifics that are relevant to the product,
								and defines variations available for the product
								(which may be used to create mult-variation listings).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerProduct</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseSellingManagerProduct -->
	<xs:element name="ReviseSellingManagerProductResponse" type="ns:ReviseSellingManagerProductResponseType"/>
	<xs:complexType name="ReviseSellingManagerProductResponseType">
		<xs:annotation>
			<xs:documentation>
				Response for revising a Selling Manager product.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SellingManagerProductDetails" type="ns:SellingManagerProductDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The details of the product.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerProduct</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseSellingManagerSaleRecord -->
	<xs:element name="ReviseSellingManagerSaleRecordRequest" type="ns:ReviseSellingManagerSaleRecordRequestType">
	</xs:element>
	<xs:complexType name="ReviseSellingManagerSaleRecordRequestType">
		<xs:annotation>
			<xs:documentation>
				Request type containing the input fields for the &lt;b&gt;ReviseSellingManagerSaleRecord&lt;/b&gt;
				call. The standard Trading API deprecation process is not applicable to this
				call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. A listing can have multiple
								order line items (transactions), but only one &lt;b&gt;ItemID&lt;/b&gt;. An &lt;b&gt;ItemID&lt;/b&gt; can be
								paired up with a corresponding &lt;b&gt;TransactionID&lt;/b&gt; and used as an input filter
								for &lt;b&gt;ReviseSellingManagerSaleRecord&lt;/b&gt;. The &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair
								corresponds to a Selling Manager &lt;b&gt;SaleRecordID&lt;/b&gt;, which can be retrieved
								with the &lt;b&gt;GetSellingManagerSaleRecord&lt;/b&gt; call. 
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;OrderLineItemID&lt;/b&gt; is used to identify a single line item order,
								or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line item
								(Combined Payment) order, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair must be
								specified. For a multiple line item (Combined Payment) order, &lt;b&gt;OrderID&lt;/b&gt;
								should be used. If &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; are specified, the
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is ignored if present in the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay order line item (transaction). An order
								line item is created once there is a commitment from a buyer to purchase
								an item. Since an auction listing can only have one order line item
								during the duration of the listing, the &lt;b&gt;TransactionID&lt;/b&gt; for
								auction listings is always 0. Along with its corresponding &lt;b&gt;ItemID&lt;/b&gt;, a
								&lt;b&gt;TransactionID&lt;/b&gt; is used and referenced during an order checkout flow and
								after checkout has been completed. The &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair can be
								used as an input filter for &lt;b&gt;ReviseSellingManagerSaleRecord&lt;/b&gt;. The
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair corresponds to a Selling Manager &lt;b&gt;SaleRecordID&lt;/b&gt;,
								which can be retrieved with the &lt;b&gt;GetSellingManagerSaleRecord&lt;/b&gt; call.
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;OrderLineItemID&lt;/b&gt; is used to identify a single line item order,
								or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line item
								(Combined Payment) order, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair must be
								specified. For a multiple line item (Combined Payment) order, &lt;b&gt;OrderID&lt;/b&gt;
								must be used. If &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; are specified, the
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is ignored if present in the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderID" type="ns:OrderIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier that identifies a single line item or multiple line
								item (Combined Payment) order. 
								&lt;br&gt;&lt;br&gt; 
								For a single line item order, the &lt;b&gt;OrderID&lt;/b&gt; value is identical to the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value that is generated upon creation of the order line
								item. For a Combined Payment order, the &lt;b&gt;OrderID&lt;/b&gt; value is created by eBay
								when the buyer or seller (sharing multiple, common order line items)
								combines multiple order line items into a Combined Payment order through
								the eBay site. A Combined Payment order can also be created by the
								seller through the &lt;b&gt;AddOrder&lt;/b&gt; call. The &lt;b&gt;OrderID&lt;/b&gt; can be used as an input
								filter for &lt;b&gt;ReviseSellingManagerSaleRecord&lt;/b&gt;. The &lt;b&gt;OrderID&lt;/b&gt;
								is linked to a Selling Manager &lt;b&gt;SaleRecordID&lt;/b&gt;, and can be retrieved
								with the &lt;b&gt;GetSellingManagerSaleRecord&lt;/b&gt; call.
								&lt;br&gt;&lt;br&gt;
								&lt;b&gt;OrderID&lt;/b&gt; overrides an &lt;b&gt;OrderLineItemID&lt;/b&gt; or &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair if
								these fields are also specified in the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingManagerSoldOrder" type="ns:SellingManagerSoldOrderType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of order costs, shipping details, order status, and
								other information. The changes made under this container will update the
								order in Selling Manager.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>								
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is a unique identifier for an eBay order line item and
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs. For a single line item order, the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value can be passed into the &lt;b&gt;OrderID&lt;/b&gt; field to revise the
								order in Selling Manager. 
								&lt;br&gt;&lt;br&gt;
								Unless an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair is used to identify a single line
								item order, or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a single or multiple line
								item (Combined Payment) order, the &lt;b&gt;OrderLineItemID&lt;/b&gt; must be specified.
								For a multiple line item (Combined Payment) order, &lt;b&gt;OrderID&lt;/b&gt; should be
								used. If &lt;b&gt;OrderLineItemID&lt;/b&gt; is specified, the &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair are
								ignored if present in the same request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50 (Note: ItemIDs and TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>ReviseSellingManagerSaleRecord</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseSellingManagerSaleRecord -->
	<xs:element name="ReviseSellingManagerSaleRecordResponse" type="ns:ReviseSellingManagerSaleRecordResponseType"/>
	<xs:complexType name="ReviseSellingManagerSaleRecordResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to a ReviseSellingManagerSaleRecord call.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseSellingManagerTemplate -->
	<xs:element name="ReviseSellingManagerTemplateRequest" type="ns:ReviseSellingManagerTemplateRequestType"/>
	<xs:complexType name="ReviseSellingManagerTemplateRequestType">
		<xs:annotation>
			<xs:documentation>
				Revises a Selling Manager template.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the sale template. You can obtain a
								SaleTemplateID by calling GetSellingManagerInventory or AddSellingManagerTemplate.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Reserved for future use.
							</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element name="SaleTemplateName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The name of the sale template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Required. In Item.ItemID, specify the same value as the
								value you specified in SaleTemplateID.
								Other child elements hold the values for properties that are being changed.
								Set values in the Item object only for those properties that are
								changing. Use DeletedField to remove a property.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeletedField" type="xs:string" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Specifies the name of a field to remove from a template.
								See the eBay Web Services guide for rules on removing values when revising items.
								Also see the relevant field descriptions to determine when to use DeletedField (and potential consequences).
								The request can contain zero, one, or many instances of DeletedField (one for each field to be removed).
								DeletedField accepts the following path names, which remove the corresponding fields:
								&lt;br&gt;&lt;br&gt;
								Item.ApplicationData&lt;br&gt;
								Item.AttributeSetArray&lt;br&gt;
								Item.ConditionID&lt;br&gt;
								Item.ItemSpecifics&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.ProStoresStoreName&lt;br&gt;
								Item.ListingCheckoutRedirectPreference.SellerThirdPartyUsername&lt;br&gt;
								Item.ListingDesigner.LayoutID&lt;br&gt;
								Item.ListingDesigner.ThemeID&lt;br&gt;
								Item.ListingEnhancement[Value]&lt;br&gt;
								Item.PayPalEmailAddress&lt;br&gt;
								Item.PictureDetails.GalleryURL&lt;br&gt;
								Item.PictureDetails.PictureURL&lt;br&gt;
								Item.PostalCode&lt;br&gt;
								Item.ProductListingDetails&lt;br&gt;
								item.ShippingDetails.PaymentInstructions&lt;br&gt;
								item.SKU&lt;br&gt;
								Item.SubTitle&lt;br&gt;&lt;br&gt;
								These values are case-sensitive. Use values that match the case of the schema element names
								(Item.PictureDetails.GalleryURL) or make the initial letter of each field name lowercase (item.pictureDetails.galleryURL).
								However, do not change the case of letters in the middle of a field name (e.g., item.picturedetails.galleryUrl is not allowed).
								&lt;br&gt;&lt;br&gt;
								Depending on how you have configured your pictures, you cannot necessarily delete
								both GalleryURL and PictureURL from an existing listing.
								If GalleryType was already set for the item you are revising, you cannot remove it.
								This means you still need to include either a first picture
								<!-- , a catalog stock photo, --> or a gallery URL in your revised listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VerifyOnly" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Use this field to verify the template instead of revising it.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ReviseSellingManagerTemplate -->
	<xs:element name="ReviseSellingManagerTemplateResponse" type="ns:ReviseSellingManagerTemplateResponseType"/>
	<xs:complexType name="ReviseSellingManagerTemplateResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the template ID and the estimated fees for the revised listing.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This sale template ID uniquely identifies the template that was revised 
								in the request. This sale template ID should match the 
								template ID specified in the request.
								specified for the call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the revised item
								listing. The fees do not include the Final Value Fee (FVF), which cannot
								be determined until an item is sold. Revising an item does not itself
								incur a fee. However, certain item properties are fee-based and result
								in the return of fees in the call's response.
								Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
									ID of the primary category in which the item was listed.
									Only returned if you set Item.CategoryMappingAllowed to true in the request
									and the ID passed in Item.PrimaryCategory was mapped to a new ID by eBay.
									If the primary category has not changed or it has expired with no replacement,
									CategoryID does not return a value.
									Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Category2ID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
									ID of the secondary category in which the item was listed.
									Only returned if you set Item.CategoryMappingAllowed to true in the request
									and the ID passed in Item.SecondaryCategory was mapped to a new ID by eBay.
									If the secondary category has not changed or it has expired with no replacement,
									Category2ID does not return a value.
									Not applicable to Half.com.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VerifyOnly" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Instead of revising, only verifies the template. 
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SaleTemplateName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The name of the sale template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellingManagerProductDetails" type="ns:SellingManagerProductDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The details of the product that this template belongs to.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ReviseSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RevokeToken -->
	<xs:element name="RevokeTokenRequest" type="ns:RevokeTokenRequestType"/>
	<xs:complexType name="RevokeTokenRequestType">
		<xs:annotation>
			<xs:documentation>
				Revokes a token before it would otherwise expire.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>FetchToken, GetSessionID, GetTokenStatus</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="UnsubscribeNotification" type="xs:boolean" minOccurs="0">
					<xs:annotation>
						<xs:documentation>
							Cancels notification subscriptions for the user/application if set to true. Default value is false.
						</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>RevokeToken</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
					</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: RevokeToken -->
	<xs:element name="RevokeTokenResponse"  type="ns:RevokeTokenResponseType"/>
	<xs:complexType name="RevokeTokenResponseType">
		<xs:annotation>
			<xs:documentation>
				Response when an application has voluntarily revoked a user token.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SaveItemToSellingManagerTemplate -->
	<xs:element name="SaveItemToSellingManagerTemplateRequest" type="ns:SaveItemToSellingManagerTemplateRequestType"/>
	<xs:complexType name="SaveItemToSellingManagerTemplateRequestType">
		<xs:annotation>
			<xs:documentation>
				Creates a Selling Manager listing template that is similar to an item.
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ItemID which should be created as a template and saved to inventory.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SaveItemToSellingManagerTemplate</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ProductID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Associates the new template with a product.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SaveItemToSellingManagerTemplate</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TemplateName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Name associated with the template. If no name is submitted, the template will be named automatically.
 							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SaveItemToSellingManagerTemplate</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SaveItemToSellingManagerTemplate -->
	<xs:element name="SaveItemToSellingManagerTemplateResponse" type="ns:SaveItemToSellingManagerTemplateResponseType"/>
	<xs:complexType name="SaveItemToSellingManagerTemplateResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of save to template operation.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="TemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Template ID that is newly created.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SaveItemToSellingManagerTemplate</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SellerReverseDispute -->
	<xs:element name="SellerReverseDisputeRequest" type="ns:SellerReverseDisputeRequestType"/>
	<xs:complexType name="SellerReverseDisputeRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to "reverse" an Unpaid Item dispute that has been closed, for
				example, if buyer and seller reach an agreement. The seller's Final Value Fee
				credit and the buyer's strike are both reversed, if applicable.
				The dispute might have resulted
				in a strike to the buyer and a Final Value Fee credit to the seller. A buyer and
				seller sometimes come to agreement after a dispute has been closed. In particular,
				the seller might discover that the buyer actually paid, or the buyer might agree
				to pay the seller's fees in exchange for having the strike removed.
				&lt;br&gt;&lt;br&gt;
				A dispute can only be reversed if it was closed with DisputeActivity set to
				SellerEndCommunication, CameToAgreementNeedFVFCredit, or
				MutualAgreementOrNoBuyerResponse.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Enables a seller to "reverse" an Unpaid Item dispute that has been
					closed, for example, if buyer and seller reach an agreement.
					The seller's Final Value Fee credit and the buyer's strike are both reversed.
					if applicable.
				</Summary>
				<RelatedCalls>
					AddDispute, AddDisputeResponse, GetDispute, GetUserDisputes
				</RelatedCalls>
				<SeeLink>
					<Title>Reversing a Closed Unpaid Item Dispute</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ReverseClosedUPIDispute</URL>
				</SeeLink>
				<SeeLink>
					<Title>Unpaid Item Disputes</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=UnpaidItemDisputes</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="DisputeID" type="ns:DisputeIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of the dispute that was returned when the dispute was created.
								The dispute must be an Unpaid Item dispute that the seller opened.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SellerReverseDispute</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DisputeResolutionReason" type="ns:DisputeResolutionReasonCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The reason the dispute is being reversed.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SellerReverseDispute</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SellerReverseDispute -->
	<xs:element name="SellerReverseDisputeResponse" type="ns:SellerReverseDisputeResponseType"/>
	<xs:complexType name="SellerReverseDisputeResponseType">
		<xs:annotation>
			<xs:documentation>
            		 Returned after calling SellerReverseDisputeRequest. Contains the status
            		 of the call and any errors or warnings.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SendInvoice -->
	<xs:element name="SendInvoiceRequest" type="ns:SendInvoiceRequestType"/>
	<xs:complexType name="SendInvoiceRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to send an order invoice to a buyer. Where applicable, updates to shipping, payment methods, and sales tax made in this request are applied to the specified order as a whole and to the individual order line items whose data are stored in individual &lt;b&gt;Transaction&lt;/b&gt; objects.
			</xs:documentation>
			<xs:appinfo>
			   <Summary>Enables a seller to send an order invoice to a buyer.</Summary>
				<RelatedCalls>AddItem, GetItemTransactions, GetSellerTransactions</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay item listing. Unless &lt;b&gt;OrderID&lt;/b&gt; or
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is provided in the request, the &lt;b&gt;ItemID&lt;/b&gt; (or &lt;b&gt;SKU&lt;/b&gt;) is
								required and must be paired with the corresponding &lt;b&gt;TransactionID&lt;/b&gt; to
								identify a single line item order. For a multiple line item (Combined
								Payment) order, &lt;b&gt;OrderID&lt;/b&gt; should be used.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for an eBay order line item (transaction). An order
								line item is created once there is a commitment from a buyer to purchase
								an item. Since an auction listing can only have one order line item
								during the duration of the listing, the &lt;b&gt;TransactionID&lt;/b&gt; for
								auction listings is always 0. Unless &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; is
								provided in the request, the &lt;b&gt;TransactionID&lt;/b&gt; is required and must be
								paired with the corresponding &lt;b&gt;ItemID&lt;/b&gt; to identify a single line item
								order. For a multiple line item (Combined Payment) order, &lt;b&gt;OrderID&lt;/b&gt; should
								be used.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. TransactionIDs are usually 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderID" type="ns:OrderIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier that identifies a single line item or multiple line
								item (Combined Payment) orders.
								&lt;br&gt;&lt;br&gt;
								For a single line item order, the &lt;b&gt;OrderID&lt;/b&gt; value is identical to the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; value that is generated upon creation of the order line
								item. For a Combined Payment order, the &lt;b&gt;OrderID&lt;/b&gt; value is created by eBay
								when the buyer or seller (sharing multiple, common order line items)
								combines multiple order line items into a Combined Payment order. A
								Combined Payment order can also be created by the seller through the
								&lt;b&gt;AddOrder&lt;/b&gt; call.
								&lt;br&gt;&lt;br&gt;
								Unless the &lt;b&gt;ItemID&lt;/b&gt; (or SKU) and corresponding &lt;b&gt;TransactionID&lt;/b&gt;, or the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; is provided in the request to identify a single line
								item order, the &lt;b&gt;OrderID&lt;/b&gt; must be specified. If &lt;b&gt;OrderID&lt;/b&gt; is specified,
								&lt;b&gt;OrderLineItemID&lt;/b&gt;, &lt;b&gt;ItemID&lt;/b&gt;, &lt;b&gt;TransactionID&lt;/b&gt;, and &lt;b&gt;SKU&lt;/b&gt; are ignored if present
								in the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>					
					<xs:element name="InternationalShippingServiceOptions" type="ns:InternationalShippingServiceOptionsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								If the buyer has an International shipping address, use this container
								to offer up to three International shipping services. If International
								shipping services are offered, (domestic) &lt;b&gt;ShippingServiceOptions&lt;/b&gt; should
								not be included in the request.
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingServiceOptions" type="ns:ShippingServiceOptionsType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								If the buyer has a domestic shipping address, use this container
								to offer up to three domestic shipping services. If domestic
								shipping services are offered, &lt;b&gt;InternationalShippingServiceOptions&lt;/b&gt; should
								not be included in the request.
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SalesTax" type="ns:SalesTaxType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of sales tax details. The amount of sales tax to
								add to the price of an order is dependent on the sales tax rate in the
								buyer's state and whether sales tax is being applied to the cost of the
								order only or the cost of the order plus shipping.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="InsuranceOption" type="ns:InsuranceOptionCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies whether an insurance fee is required. An &lt;b&gt;InsuranceOption&lt;/b&gt; value of
								&lt;b&gt;IncludedInShippingHandling&lt;/b&gt; cannot be used if the item will use calculated
								shipping. Some shipping carriers automatically include shipping insurance
								for qualifying items.&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<AllValuesExcept>NotOfferedOnSite</AllValuesExcept>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>Determining Shipping Costs for a Listing</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ShippingGettingCosts</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="InsuranceFee" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Insurance cost, as set by seller, if ShippingType = 1.
								Specify if &lt;b&gt;InsuranceOption&lt;/b&gt; is optional or required. Must
								be greater than zero value if a value of Optional or Required is passed in
								&lt;b&gt;InsuranceOption&lt;/b&gt;. Value specified should be the total cost of insuring the
								item.&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<Default>0.0</Default>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>Determining Shipping Costs for a Listing</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ShippingGettingCosts</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PaymentMethods" type="ns:BuyerPaymentMethodCodeType" minOccurs="0"  maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								This optional field allows a US or German seller to add specific payment
								methods that were not in the original item listing. The only valid values
								for this field are 'PayPal' for a US listing, or
								'MoneyXferAcceptedInCheckout' (CIP+) for a DE listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PayPalEmailAddress" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If the &lt;b&gt;PaymentMethods&lt;/b&gt; field is used and set to PayPal, the seller
								provides his/her PayPal email address in this field.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CheckoutInstructions" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								 This field allows the seller to provide a message or instructions
								 regarding checkout/payment or the return policy.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>500</MaxLength>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EmailCopyToSeller" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Flag indicating whether or not the seller wishes to receive an email copy of
								the invoice sent to the buyer.
							</xs:documentation>
							<xs:appinfo>
								<default>true</default>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CODCost" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This dollar value indicates the money due from the buyer upon delivery of the item.
								&lt;br&gt;&lt;br&gt;
								This field should only be specified in the &lt;b&gt;SendInvoice&lt;/b&gt; request if 'COD' 
								(cash-on-delivery) was the payment method selected by the buyer and it is included
								as the &lt;b&gt;PaymentMethods&lt;/b&gt; value in the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>Other Shipping Features</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=CODInShippingDetails</URL>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The seller's unique identifier for an item that is being tracked by this
								SKU. If &lt;b&gt;OrderID&lt;/b&gt; or &lt;b&gt;OrderLineItemID&lt;/b&gt; are not provided, both &lt;b&gt;SKU&lt;/b&gt; (or
								&lt;b&gt;ItemID&lt;/b&gt;) and corresponding &lt;b&gt;TransactionID&lt;/b&gt; must be provided to uniquely
								identify a single line item order. For a multiple line item (Combined
								Payment) order, &lt;b&gt;OrderID&lt;/b&gt; must be used.
								&lt;br&gt;
								&lt;br&gt;
								This field can only be used if the &lt;b&gt;Item.InventoryTrackingMethod&lt;/b&gt; field
								(set with the &lt;b&gt;AddFixedPriceItem&lt;/b&gt; or &lt;b&gt;RelistFixedPriceItem&lt;/b&gt; calls) is set to
								SKU.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50</MaxLength>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique identifier for an eBay order line item. This field is created
								as soon as there is a commitment to buy from the seller, and its value
								is based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a
								hyphen in between these two IDs.
								&lt;br&gt;
								&lt;br&gt;
								Unless the &lt;b&gt;ItemID&lt;/b&gt; (or &lt;b&gt;SKU&lt;/b&gt;) and corresponding &lt;b&gt;TransactionID&lt;/b&gt; is used to
								identify a single line item order, or the &lt;b&gt;OrderID&lt;/b&gt; is used to identify a
								single or multiple line item (Combined Payment) order, the
								&lt;b&gt;OrderLineItemID&lt;/b&gt; must be specified. For a multiple line item (Combined
								Payment) order, &lt;b&gt;OrderID&lt;/b&gt; should be used. If &lt;b&gt;OrderLineItemID&lt;/b&gt; is specified,
								&lt;b&gt;ItemID&lt;/b&gt;, &lt;b&gt;TransactionID&lt;/b&gt;, and &lt;b&gt;SKU&lt;/b&gt; are ignored if present in the same
								request.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>50 (Note: ItemIDs and TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
								<CallInfo>
									<CallName>SendInvoice</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AdjustmentAmount" type="ns:AmountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field allows the seller to adjust the total cost of the order to account
								for an extra charge or to pass down a discount to the buyer. 
								&lt;br&gt;&lt;br&gt;
								The currency used in this field must be the same currency of the listing site.
								A positive value in this field indicates that the amount is an extra charge
								being paid to the seller by the buyer, and a negative value indicates that the
								amount is a discount given to the buyer by the seller. 
						  </xs:documentation>
					    <xs:appinfo>													
						    <CallInfo>
					      	<CallName>SendInvoice</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SendInvoice -->
	<xs:element name="SendInvoiceResponse" type="ns:SendInvoiceResponseType"/>
	<xs:complexType name="SendInvoiceResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of calling SendInvoice.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetMessagePreferences -->
	<xs:element name="SetMessagePreferencesRequest" type="ns:SetMessagePreferencesRequestType"/>
	<xs:complexType name="SetMessagePreferencesRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to add custom Ask Seller a Question (ASQ) subjects to their
				Ask a Question page, or to reset any custom subjects to their default values.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetMessagePreferences</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ASQPreferences" type="ns:ASQPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains custom ASQ subjects or a flag to reset those
								subjects to their default values.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetMessagePreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetMessagePreferences -->
	<xs:element name="SetMessagePreferencesResponse" type="ns:SetMessagePreferencesResponseType"/>
	<xs:complexType name="SetMessagePreferencesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the success or failure of the
				SetMessagePreferencesRequest, and any applicable errors.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence/>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetNotificationPreferences -->
	<xs:element name="SetNotificationPreferencesRequest"	type="ns:SetNotificationPreferencesRequestType"/>
	<xs:complexType name="SetNotificationPreferencesRequestType">
		<xs:annotation>
			<xs:documentation>
				Manages notification and alert preferences for applications and users.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetNotificationPreferences, GetNotificationsUsage</RelatedCalls>
				<SeeLink>
					<Title>Working with Platform Notifications</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=PlatformNotifications</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ApplicationDeliveryPreferences" type="ns:ApplicationDeliveryPreferencesType" minOccurs="0">
						<xs:annotation>
		 					<xs:documentation>
								Specifies application-level event preferences that have been enabled,
								including the URL to which notifications should be delivered and whether
								notifications should be enabled or disabled (although the
								UserDeliveryPreferenceArray input property specifies specific
								notification subscriptions).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetNotificationPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserDeliveryPreferenceArray" type="ns:NotificationEnableArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies events and whether or not they are enabled.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetNotificationPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserData" type="ns:NotificationUserDataType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies user data for notification settings, such as mobile phone number.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetNotificationPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EventProperty" type="ns:NotificationEventPropertyType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								Characteristics or details of an event such as type, name and value.
								Currently can only be set for wireless applications.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetNotificationPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DeliveryURLName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies up to 25 ApplicationDeliveryPreferences.DeliveryURLDetails.DeliveryURLName
								to associate with a user token sent in a SetNotificationPreferences request. To
								specify multiple DeliveryURLNames, create separate instances of
								ApplicationDeliveryPreferences.DeliveryURLDetails.DeliveryURLName, and then enable
								up to 25 DeliveryURLNames by including them in comma-separated format in this field.
							</xs:documentation>
							<xs:appinfo>
							<CallInfo>
								<CallName>SetNotificationPreferences</CallName>
								<RequiredInput>No</RequiredInput>
							</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetNotificationPreferences -->
	<xs:element name="SetNotificationPreferencesResponse"  type="ns:SetNotificationPreferencesResponseType"/>
	<xs:complexType name="SetNotificationPreferencesResponseType">
		<xs:annotation>
			<xs:documentation>
				(out) Returns the success or failure of a SetNotificationPreferences request.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetPromotionalSale -->
	<xs:element name="SetPromotionalSaleRequest" type="ns:SetPromotionalSaleRequestType"/>
	<xs:complexType name="SetPromotionalSaleRequestType">
		<xs:annotation>
			<xs:documentation>
				Creates or modifies a promotional sale. Promotional sales enable sellers
				to apply discounts and/or free shipping across many listings.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Creates or modifies a promotional sale. Promotional sales enable sellers
					to apply discounts and/or free shipping across many listings.
				</Summary>
				<RelatedCalls>SetPromotionalSaleListings, GetPromotionalSaleDetails</RelatedCalls>
				<SeeLink>
					<Title>Putting Store Items on Sale</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=PuttingItemsOnSale</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Action" type="ns:ModifyActionCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The seller must include this field and set it to 'Add' to create a new 
								promotional sale, or set it to 'Update' to modify an existing promotional sale, 
								or set it to 'Delete' to delete a promotional sale.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSale</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionalSaleDetails" type="ns:PromotionalSaleType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container must be included in each &lt;b&gt;SetPromotionalSale&lt;/b&gt; call. 
								The fields of this container that will be used will depend on whether the seller is 
								adding a new promotional sale, updating an existing promotional sale, or deleting an 
								existing promotional sale.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSale</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetPromotionalSale -->
	<xs:element name="SetPromotionalSaleResponse" type="ns:SetPromotionalSaleResponseType"/>
	<xs:complexType name="SetPromotionalSaleResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the ID and status of a promotional sale.
				The Promotional Price Display feature enables sellers
				to apply discounts and/or free shipping across many listings.  
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Status" type="ns:PromotionalSaleStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the status of a promotional sale.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSale</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionalSaleID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the ID of a promotional sale.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSale</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetPromotionalSaleListings -->
	<xs:element name="SetPromotionalSaleListingsRequest" type="ns:SetPromotionalSaleListingsRequestType"/>
	<xs:complexType name="SetPromotionalSaleListingsRequestType">
		<xs:annotation>
			<xs:documentation>
				Defines the &lt;b&gt;SetPromotionalSaleListings&lt;/b&gt; call request. 
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>SetPromotionalSale, GetPromotionalSaleDetails</RelatedCalls>
				<SeeLink>
					<Title>Putting Store Items on Sale</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=PuttingItemsOnSale</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="PromotionalSaleID" type="xs:long"  minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The unique identifier of the seller's promotional sale. Based on the &lt;b&gt;Action&lt;/b&gt; 
								value, listings will either be added to or removed from the promotional sale.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Action" type="ns:ModifyActionCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This required field determines whether you are adding (specify 'Add') or
								removing (specify 'Delete) one or more listings from the promotional sale
								identified by the &lt;b&gt;PromotionalSaleID&lt;/b&gt; value in the request.
								&lt;br&gt;&lt;br&gt;
								If you specify 'Delete', you must include one or more &lt;b&gt;ItemID&lt;/b&gt;
								values under the &lt;b&gt;PromotionalSaleItemIDArray&lt;/b&gt; container, and
								you cannot use the other filter options in the request. If you specify 'Add',
								you can add one or more listings using any of the filtering options in the
								request. Active auction listings that have one or more bids cannot be added to
								or removed from a promotional sale.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<OnlyTheseValues>Add, Delete</OnlyTheseValues>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionalSaleItemIDArray" type="ns:ItemIDArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of one or more &lt;b&gt;ItemID&lt;/b&gt; values. Based on
								the &lt;b&gt;Action&lt;/b&gt; value, the listings identified by these 
								&lt;b&gt;ItemID&lt;/b&gt; values are either added to or removed from the 
								promotional sale.
								&lt;br&gt;&lt;br&gt;
								This container is required if listings are being removed (&lt;b&gt;Action&lt;/b&gt;='Delete') 
								from the promotional sale.
  						</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StoreCategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If a &lt;b&gt;StoreCategoryID&lt;/b&gt; value is included in the call request,
								all active items in this store category are added to the promotional sale. This
								field cannot be used if the &lt;b&gt;Action&lt;/b&gt; field is set to 'Delete'.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If a &lt;b&gt;CategoryID&lt;/b&gt; value is included in the call request,
								all active items in this eBay category are added to the promotional sale. This
								field cannot be used if the &lt;b&gt;Action&lt;/b&gt; field is set to 'Delete'.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AllFixedPriceItems" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If this field is included and set to 'true' in the call request, all fixed-price
								listings are added to the promotional sale. This field cannot be used if the
								&lt;b&gt;Action&lt;/b&gt; field is set to 'Delete'.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AllStoreInventoryItems" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If this field is included and set to 'true' in the call request, all store inventory
								items are added to the promotional sale. This field cannot be used if the
								&lt;b&gt;Action&lt;/b&gt; field is set to 'Delete'.
						</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AllAuctionItems" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								If this field is included and set to 'true' in the call request, all auction
								listings are added to the promotional sale. This field cannot be used if the
								&lt;b&gt;Action&lt;/b&gt; field is set to 'Delete'.
						</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetPromotionalSaleListings -->
	<xs:element name="SetPromotionalSaleListingsResponse" type="ns:SetPromotionalSaleListingsResponseType"/>
	<xs:complexType name="SetPromotionalSaleListingsResponseType">
		<xs:annotation>
			<xs:documentation>
          Contains the status of a promotional sale.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="Status" type="ns:PromotionalSaleStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the status of a promotional sale.
							</xs:documentation>
							<xs:appinfo>								
								<CallInfo>
									<CallName>SetPromotionalSaleListings</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetSellingManagerFeedbackOptions -->
	<xs:element name="SetSellingManagerFeedbackOptionsRequest" type="ns:SetSellingManagerFeedbackOptionsRequestType"/>
	<xs:complexType name="SetSellingManagerFeedbackOptionsRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables Selling Manager subscribers to store standard feedback comments that can
				be left for their buyers. Selling Manager Pro subscribers can also specify what
				events, if any, will trigger an automated feedback to buyers.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Enables Selling Manager and Selling Manager Pro subscribers to store feedback
					comments for buyers and set automated feedback preferences (Selling Manager Pro
					subscribers only).
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
				<SeeLink>
					<Title>Leaving and Retrieving Feedback</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Feedback</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="AutomatedLeaveFeedbackEvent" type="ns:AutomatedLeaveFeedbackEventCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the event that will trigger automated feedback to the buyer.
								Applies to Selling Manager Pro subscribers only.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerFeedbackOptions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="StoredComments" type="ns:FeedbackCommentArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains a set of comments from which one can be selected to leave
								feedback for a buyer. If automated feedback is used, a comment is
								selected from the set randomly. Automated feedback applies to Selling
								Manager Pro subscribers only. Stored comments cannot be replaced or
								edited individually. Submitting a stored comments array replaces all
								existing stored comments.
								&lt;br&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerFeedbackOptions</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetSellingManagerFeedbackOptions -->
	<xs:element name="SetSellingManagerFeedbackOptionsResponse" type="ns:SetSellingManagerFeedbackOptionsResponseType"/>
	<xs:complexType name="SetSellingManagerFeedbackOptionsResponseType">
		<xs:annotation>
			<xs:documentation>
				Provides confirmation that feedback comments and (optionally) automated feedback 
				preferences were added successfully.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetSellingManagerItemAutomationRule -->
	<xs:element name="SetSellingManagerItemAutomationRuleRequest" type="ns:SetSellingManagerItemAutomationRuleRequestType">
	</xs:element>
	<xs:complexType name="SetSellingManagerItemAutomationRuleRequestType">
		<xs:annotation>
			<xs:documentation>
				Revises, or adds to, the set of Selling Manager automation
				rules associated with an item.
				&lt;br&gt;
				&lt;br&gt;
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
				&lt;br&gt;
				&lt;br&gt;
				Using this call, you can add an autolist rule.
				You also can add a second chance offer
				rule (restricted to auction items and auction templates).
				Note that autorelist rules can only be set on templates.
				An autorelist rule for an item is inherited from a template.
				&lt;br&gt;
				&lt;br&gt;
				This call also enables you to specify particular information about automation
				rules.
				&lt;br&gt;
				&lt;br&gt;
				If a node is not passed in the call, the setting for the corresponding
				automation rule remains unchanged.
				&lt;br&gt;
				&lt;br&gt;
				Although this call can revise (overwrite) an existing rule,
				this call cannot delete an automation rule.
				(Instead, use DeleteSellingManagerItemAutomationRule.)
			</xs:documentation>
			<xs:appinfo>
				<Summary>
						Revises or adds to the set of
					Selling Manager automation rules associated with a specific item.
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The item ID whose automation rules you want to change.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerItemAutomationRule</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedRelistingRule" type="ns:SellingManagerAutoRelistType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated relisting rule to be associated with the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerItemAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedSecondChanceOfferRule" type="ns:SellingManagerAutoSecondChanceOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated second chance offer rule to be associated with the item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerItemAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetSellingManagerItemAutomationRule -->
	<xs:element name="SetSellingManagerItemAutomationRuleResponse" type="ns:SetSellingManagerItemAutomationRuleResponseType"/>
	<xs:complexType name="SetSellingManagerItemAutomationRuleResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the set of automation rules associated with the specified item.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AutomatedListingRule" type="ns:SellingManagerAutoListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the automated listing rule associated with this item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedRelistingRule" type="ns:SellingManagerAutoRelistType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the automated relisting rule associated with this item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedSecondChanceOfferRule" type="ns:SellingManagerAutoSecondChanceOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the automated second chance offer rule associated with this item.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains fees that may be incurred when items are listed using the 
								automation rules (e.g., a scheduled listing fee). Use of an automation rule 
								does not in itself have a fee, but use can result in a fee.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerItemAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetSellingManagerTemplateAutomationRule -->
	<xs:element name="SetSellingManagerTemplateAutomationRuleRequest" type="ns:SetSellingManagerTemplateAutomationRuleRequestType">
	</xs:element>
	<xs:complexType name="SetSellingManagerTemplateAutomationRuleRequestType">
		<xs:annotation>
			<xs:documentation>
				Revises, or adds to, the Selling Manager automation
				rules associated with a template.
				&lt;br&gt;
				&lt;br&gt;
				This call is subject to change without notice; the
				deprecation process is inapplicable to this call.
				&lt;br&gt;
				&lt;br&gt;
				Using this call, you can add either an autorelist rule or
				an autolist rule, but not both.
				You also can add a second chance
				offer rule (restricted to auction items and auction templates).
				&lt;br&gt;
				&lt;br&gt;
				This call also enables you to specify particular information about automation
				rules.
				&lt;br&gt;
				&lt;br&gt;
				If a node is not passed in the call, the setting for the corresponding
				automation rule remains unchanged.
				&lt;br&gt;
				&lt;br&gt;
				Although this call can revise (overwrite) an existing rule,
				this call cannot delete an automation rule.
				(Instead, use DeleteSellingManagerTemplateAutomationRule.)
			</xs:documentation>
			<xs:appinfo>
				<Summary>
						Revises or adds to the
					Selling Manager automation rules associated with a specific template.
				</Summary>
				<RelatedCalls>AddSellingManagerTemplate,GetSellingManagerTemplates,GetSellingManagerTemplateAutomationRule,DeleteSellingManagerTemplateAutomationRule</RelatedCalls>
				<SeeLink>
					<Title>Using Selling Manager Calls in the Trading API</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SellingManagerApps</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager/</URL>
				</SeeLink>
				<SeeLink>
					<Title>Selling Manager Pro page on the eBay Site</Title>
					<URL>http://pages.ebay.com/selling_manager_pro</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="SaleTemplateID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The ID of the Selling Manager template whose automation rules
								you want to change. You can obtain a SaleTemplateID by calling
								GetSellingManagerInventory.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedListingRule" type="ns:SellingManagerAutoListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated listing rule to be associated with the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedRelistingRule" type="ns:SellingManagerAutoRelistType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated relisting rule to be associated with the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedSecondChanceOfferRule" type="ns:SellingManagerAutoSecondChanceOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The information for the automated second chance offer rule to be associated with the template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerTemplateAutomationRule</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetSellingManagerTemplateAutomationRule -->
	<xs:element name="SetSellingManagerTemplateAutomationRuleResponse" type="ns:SetSellingManagerTemplateAutomationRuleResponseType"/>
	<xs:complexType name="SetSellingManagerTemplateAutomationRuleResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains the set of automation rules associated with the specified template.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="AutomatedListingRule" type="ns:SellingManagerAutoListType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the automated listing rule associated with this template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedRelistingRule" type="ns:SellingManagerAutoRelistType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the automated relisting rule associated with this template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="AutomatedSecondChanceOfferRule" type="ns:SellingManagerAutoSecondChanceOfferType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains the automated second chance offer rule associated with this template.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains fees that may be incurred when items are listed using the 
								automation rules (e.g., a scheduled listing fee). Use of an automation rule 
								does not in itself have a fee, but use can result in a fee.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetSellingManagerTemplateAutomationRule</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetShippingDiscountProfiles -->
	<xs:element name="SetShippingDiscountProfilesRequest" type="ns:SetShippingDiscountProfilesRequestType"/>
	<xs:complexType name="SetShippingDiscountProfilesRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to define shipping cost discount profiles for things such as combined
				payments for shipping and handling costs.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					AddItem, GetItem, GetShippingDiscountProfiles, RelistItem, ReviseItem, VerifyAddItem
				</RelatedCalls>
				<SeeLink>
					<Title>Other Shipping Features</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ShippingDiscountProfiles</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CurrencyID" type="ns:CurrencyCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The three-digit code of the currency to be used for shipping cost discounts and
								insurance for combined payment orders. A discount profile can only be associated
								with a listing if the &lt;b&gt;CurrencyID&lt;/b&gt; value of the profile matches the 
								&lt;b&gt;Item.Currency&lt;/b&gt; value specified in a listing.
								&lt;br&gt;&lt;br&gt;
								Required if the user creates flat rate shipping discount profiles, a promotional
								discount, a packaging/handling cost profile based on a variable
								discount rule, or if the user defines shipping insurance range/fee pairs.
								&lt;br&gt;&lt;br&gt;
								Note: There is a currencyID attribute on many elements of SetShippingDiscountProfiles.
								To avoid an error, be sure to use the same &lt;b&gt;CurrencyID&lt;/b&gt; value 
								in each occurrence within the same request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CombinedDuration" type="ns:CombinedPaymentPeriodCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This field is used to specify the number of days after the sale of an
								item in which the buyer or seller can combine multiple and mutual order
								line items into one Combined Payment order. In a Combined Payment order,
								the buyer makes one payment for all order line items, hence only unpaid
								order line items can be combined into a Combined Payment order.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ModifyActionCode" type="ns:ModifyActionCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates what action to take on the specified flat shipping discount,
								calculated shipping discount or promotional discount.
								If the action is Delete and if a flat rate or calculated shipping discount
								profile is specified, the discount profile identified by
								DiscountProfile.DiscountProfileID is deleted
								(see DiscountProfile.MappedDiscountProfileID for related details).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="FlatShippingDiscount" type="ns:FlatShippingDiscountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Details of a shipping cost discount profile for flat rate shipping.
								If this is provided, CalculatedShippingDiscount and PromotionalShippingDiscountDetails
								should be omitted.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CalculatedShippingDiscount" type="ns:CalculatedShippingDiscountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Details of a shipping cost discount profile for calculated shipping.
								If this is provided, FlatShippingDiscount and PromotionalShippingDiscountDetails
								should be omitted.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CalculatedHandlingDiscount" type="ns:CalculatedHandlingDiscountType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container is used by the seller to specify/modify packaging and handling discounts that are applied 
								for combined payment orders.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PromotionalShippingDiscountDetails" type="ns:PromotionalShippingDiscountDetailsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The data for the promotional shipping discount.
								If this is provided, FlatShippingDiscount and CalculatedShippingDiscount
								should be omitted.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ShippingInsurance" type="ns:ShippingInsuranceType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Information establishing what fee to apply for domestic shipping insurance
								for combined payment depending on which range the order item-total price
								falls into.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="InternationalShippingInsurance" type="ns:ShippingInsuranceType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Information establishing what fee to apply for international shipping
								insurance for combined payment depending on which range the order item-total
								price falls into.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetShippingDiscountProfiles</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetShippingDiscountProfiles -->
	<xs:element name="SetShippingDiscountProfilesResponse" type="ns:SetShippingDiscountProfilesResponseType"/>
	<xs:complexType name="SetShippingDiscountProfilesResponseType">
		<xs:annotation>
			<xs:documentation>
				The response to a call of SetShippingDiscountProfiles.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetStore -->
	<xs:element name="SetStoreRequest" type="ns:SetStoreRequestType"/>
	<xs:complexType name="SetStoreRequestType">
		<xs:annotation>
			<xs:documentation>
				Sets the configuration of the eBay store owned by the caller.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>
					GetStoreOptions, GetStore, GetStoreCustomPage, SetStoreCustomPage,
					SetStoreCategories, GetStoreCategoryUpdateStatus
				</RelatedCalls>
				<SeeLink>
					<Title>Editing the Store Settings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=EditingStoreSettings</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Store" type="ns:StoreType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
					      Specifies the Store configuration that is being set for the user.
					    </xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStore</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetStore -->
	<xs:element name="SetStoreResponse" type="ns:SetStoreResponseType"/>
	<xs:complexType name="SetStoreResponseType">
	  <xs:annotation>
	    <xs:documentation>
	      Returned after calling SetStoreRequest. This serves as confirmation that
        the Store configuration was successfully submitted.
	    </xs:documentation>
	  </xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetStoreCategories -->
	<xs:element name="SetStoreCategoriesRequest" type="ns:SetStoreCategoriesRequestType"/>
	<xs:complexType name="SetStoreCategoriesRequestType">
		<xs:annotation>
			<xs:documentation>
				Changes the category structure of an eBay store.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetStore, GetStoreCategoryUpdateStatus, SetStore</RelatedCalls>
				<SeeLink>
					<Title>Managing eBay Stores</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingeBayStores</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Action" type="ns:StoreCategoryUpdateActionCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the type of action (Add, Move, Delete, or Rename) to carry out
								for the specified categories.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCategories</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ItemDestinationCategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Items can only be contained within child categories. A parent category
								cannot contain items. If adding, moving, or deleting categories displaces
								items, you must specify a destination child category under which the
								displaced items will be moved. The destination category must have no
								child categories.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCategories</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DestinationParentCategoryID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								When adding or moving store categories, specifies the category under
								which the listed categories will be located. To add or move categories to
								the top level, set the value to -999.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCategories</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element  name="StoreCategories"  type="ns:StoreCustomCategoryArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the store categories on which to act.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCategories</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetStoreCategories -->
	<xs:element name="SetStoreCategoriesResponse" type="ns:SetStoreCategoriesResponseType"/>
	<xs:complexType name="SetStoreCategoriesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of the processing progress for changes to the category
				structure for a store.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="TaskID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The task ID associated with the category structure change request. For a
								simple change, the SetStoreCategories call is processed synchronously.
								That is, simple changes are made immediately and then the response is
								returned. For synchronous processing, the task ID in the response is 0.
								If the category structure changes affect many listings, the changes will
								be processed asynchronously and the task ID will be a positive number.
								Use the non-zero task ID with GetStoreCategoryUpdateStatus to monitor
								the status of asynchronously processed changes.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCategories</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Status" type="ns:TaskStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								When a category structure change is processed synchronously, the status
								is returned as Complete or Failed. For asynchronously processed changes,
								the status is reported as Pending. Use GetStoreCategoryUpdateStatus to
								monitor the status of asynchronously processed changes.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCategories</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
						<!-- Done/Queued/InProgress/Failed -->
					</xs:element>
					<xs:element name="CustomCategory" type="ns:StoreCustomCategoryArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Contains data for store categories that you have created.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCategories</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetStoreCustomPage -->
	<xs:element name="SetStoreCustomPageRequest" type="ns:SetStoreCustomPageRequestType"/>
	<xs:complexType name="SetStoreCustomPageRequestType">
		<xs:annotation>
			<xs:documentation>
	      Creates or updates a custom page on a user's eBay Store.
	    </xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetStoreOptions, GetStore, SetStore, GetStoreCustomPage</RelatedCalls>
				<SeeLink>
					<Title>Managing Custom Pages</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingCustomPages</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="CustomPage" type="ns:StoreCustomPageType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
	   				  	The custom page being submitted.
	  					</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCustomPage</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetStoreCustomPage -->
	<xs:element name="SetStoreCustomPageResponse" type="ns:SetStoreCustomPageResponseType"/>
	<xs:complexType name="SetStoreCustomPageResponseType">
	  <xs:annotation>
	    <xs:documentation>
	      Returned after calling SetStoreCustomPageRequest. This serves as
	      confirmation that the custom page was successfully submitted.
	    </xs:documentation>
	  </xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="CustomPage" type="ns:StoreCustomPageType" minOccurs="0">
		  			<xs:annotation>
	    				<xs:documentation>
	   				  	The custom page that was submitted.
	  					</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStoreCustomPage</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetStorePreferences -->
	<xs:element name="SetStorePreferencesRequest" type="ns:SetStorePreferencesRequestType"/>
	<xs:complexType name="SetStorePreferencesRequestType">
		<xs:annotation>
			<xs:documentation>
				Sets the preferences for a user's eBay Store.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetStore, GetStorePreferences, SetStore</RelatedCalls>
				<SeeLink>
					<Title>Managing eBay Stores</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingeBayStores</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="StorePreferences" type="ns:StorePreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
					      Specifies the store preferences.
					    </xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetStorePreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetStorePreferences -->
	<xs:element name="SetStorePreferencesResponse" type="ns:SetStorePreferencesResponseType"/>
	<xs:complexType name="SetStorePreferencesResponseType">
		<xs:annotation>
			<xs:documentation>
	      Returned after calling SetStorePreferencesRequest. This serves as confirmation that 
        the Store preferences were successfully submitted.
	    </xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetTaxTable -->
	<xs:element name="SetTaxTableRequest" type="ns:SetTaxTableRequestType"/>
	<xs:complexType name="SetTaxTableRequestType">
		<xs:annotation>
			<xs:documentation>
				Sets the tax table for a seller on a given site.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetTaxTable</RelatedCalls>
				<SeeLink>
					<Title>Enabling Multi-jurisdiction Sales Tax</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SalesTax</URL>
				</SeeLink>
				<SeeLink>
					<Title>Managing User Preferences</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SettingUserPreferences</URL>
				</SeeLink>
				<SeeLink>
					<Title>Enabling Multi-jurisdiction Sales Tax</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SalesTax</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="TaxTable" type="ns:TaxTableType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A container of tax jurisdiction information unique to a user/site combination.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetTaxTable</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetTaxTable -->
	<xs:element name="SetTaxTableResponse" type="ns:SetTaxTableResponseType"/>
	<xs:complexType name="SetTaxTableResponseType">
		<xs:annotation>
			<xs:documentation>
				Response to SetTaxTableRequest.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetUserNotes -->
	<xs:element name="SetUserNotesRequest" type="ns:SetUserNotesRequestType"/>
	<xs:complexType name="SetUserNotesRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables users to add, replace, and delete My eBay notes for
				items that are being tracked in the My eBay All Selling and
				All Buying areas.
			</xs:documentation>
			<xs:appinfo>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								ID of the item to which the My eBay note will be
								attached. Notes can only be added to items that are
								currently being tracked in My eBay.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. ItemIDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>SetUserNotes</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Action" type="ns:SetUserNotesActionCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The seller must include this field and set it to 'AddOrUpdate' to add a new 
								user note or update an existing user note, or set it to 'Delete' to delete a 
								an existing user note.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserNotes</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="NoteText" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Text of the note. Maximum 250 characters. Required only
								if the Action is &lt;b&gt;AddOrUpdate&lt;/b&gt;. This note text will
								completely replace any existing My eBay note for the
								specified item.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>250</MaxLength>
								<CallInfo>
									<CallName>SetUserNotes</CallName>
									<RequiredInput>Conditionally</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="TransactionID" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Unique identifier for the order line item (transaction) to which the My
								eBay note will be attached. Notes can only be added to order line items
								that are currently being tracked in My eBay. Buyers can
								view user notes made on order line items in the
								&lt;b&gt;PrivateNotes&lt;/b&gt; field of the &lt;b&gt;WonList&lt;/b&gt; container in &lt;b&gt;GetMyeBayBuying&lt;/b&gt;, and
								sellers can view user notes made on order line items in
								the &lt;b&gt;PrivateNotes&lt;/b&gt; field of the &lt;b&gt;SoldList&lt;/b&gt; and &lt;b&gt;DeletedFromSoldList&lt;/b&gt;
								containers in &lt;b&gt;GetMyeBaySellinging&lt;/b&gt;.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserNotes</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VariationSpecifics" type="ns:NameValueListArrayType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of name-value pairs that identify (match) one
								variation within a fixed-price, multi-variation listing. The specified
								name-value pair(s) must exist in the listing specified by either the
								&lt;b&gt;ItemID&lt;/b&gt; or &lt;b&gt;SKU&lt;/b&gt; values specified in the request. If a specific order line
								item is targeted in the request with an
								&lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair or an &lt;b&gt;OrderLineItemID&lt;/b&gt; value, any specified
								&lt;b&gt;VariationSpecifics&lt;/b&gt; container is ignored by the call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserNotes</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								SKU value of the item variation to which the My eBay note will be
								attached. Notes can only be added to items that are currently being
								tracked in My eBay. A SKU (stock keeping unit) value is defined by and
								used by the seller to identify a variation within a fixed-price, multi-
								variation listing. The SKU value is assigned to a variation of an item
								through the &lt;b&gt;Variations.Variation.SKU&lt;/b&gt; element.
								&lt;br&gt;
								&lt;br&gt;
								This field can only be used if the &lt;b&gt;Item.InventoryTrackingMethod&lt;/b&gt; field
								(set with the &lt;b&gt;AddFixedPriceItem&lt;/b&gt; or &lt;b&gt;RelistFixedPriceItem&lt;/b&gt; calls) is set to
								SKU.
								&lt;br&gt;
								&lt;br&gt;
								If a specific order line item is targeted in the request
								with an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair or an &lt;b&gt;OrderLineItemID&lt;/b&gt; value, any
								specified &lt;b&gt;SKU&lt;/b&gt; is ignored by the call.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserNotes</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="OrderLineItemID" type="xs:string" minOccurs="0">
						<xs:annotation>
						<xs:documentation>
							A unique identifier for an eBay order line item. This field is created as
							soon as there is a commitment to buy from the seller, and its value is
							based upon the concatenation of &lt;b&gt;ItemID&lt;/b&gt; and &lt;b&gt;TransactionID&lt;/b&gt;, with a hyphen in
							between these two IDs. &lt;b&gt;OrderLineItemID&lt;/b&gt; can be used in the input instead of
							an &lt;b&gt;ItemID&lt;/b&gt;/&lt;b&gt;TransactionID&lt;/b&gt; pair to identify an order line item. 
							&lt;br&gt;
							&lt;br&gt;
							Notes can only be added to order line items that are currently being
							tracked in My eBay. Buyers can view user notes made on order line items in
							the &lt;b&gt;PrivateNotes&lt;/b&gt; field of the &lt;b&gt;WonList&lt;/b&gt; container in &lt;b&gt;GetMyeBayBuying&lt;/b&gt;, and
							sellers can view user notes made on order line items in the &lt;b&gt;PrivateNotes&lt;/b&gt;
							field of the &lt;b&gt;SoldList&lt;/b&gt; and &lt;b&gt;DeletedFromSoldList&lt;/b&gt; containers in
							&lt;b&gt;GetMyeBaySellinging&lt;/b&gt;.
						</xs:documentation>
						<xs:appinfo>
							<MaxLength>50 (Note: ItemIDs and TransactionIDs usually consist of 9 to 12 digits.)</MaxLength>
							<CallInfo>
								<CallName>SetUserNotes</CallName>
								<RequiredInput>Conditionally</RequiredInput>
							</CallInfo>
						</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetUserNotes -->
	<xs:element name="SetUserNotesResponse" type="ns:SetUserNotesResponseType"/>
	<xs:complexType name="SetUserNotesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the status of the call.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType"/>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetUserPreferences -->
	<xs:element name="SetUserPreferencesRequest" type="ns:SetUserPreferencesRequestType"/>
	<xs:complexType name="SetUserPreferencesRequestType">
		<xs:annotation>
			<xs:documentation>
				Defines the &lt;b&gt;SetUserPreferences&lt;/b&gt; request container.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetUserPreferences</RelatedCalls>
				<SeeLink>
					<Title>Managing User Preferences</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ManagingUserPreferences</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="BidderNoticePreferences" type="ns:BidderNoticePreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's preference for receiving contact
								information for unsuccessful bidders. This preference is only applicable for
								auction listings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CombinedPaymentPreferences" type="ns:CombinedPaymentPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's preference for allowing combined payment
								on multiple orders shared between the same seller and buyer.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
								Calculated and flat-rate shipping preferences are no longer set using this
								call. Instead, use the &lt;b&gt;SetShippingDiscountProfiles&lt;/b&gt; call to
								set the shipping discounts for combined payment orders.
								&lt;/span&gt;
								&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;strong&gt;Note:&lt;/strong&gt;
								A seller's combined payment preferences can take up to 7 days to
								have any logical or functional effect on eBay.
								&lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="CrossPromotionPreferences" type="ns:CrossPromotionPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								This container should no longer be used as eBay Store Cross Promotions are no
								longer supported in the Trading API. This container will be removed from the
								Trading WSDL and API Call Reference docs in a future release.
								&lt;br&gt;&lt;br&gt;
								Container consisting of the seller's cross-promotion preferences. These
								preferences are only applicable for eBay Store owners. One or more
								preferences may be set or modified under this field.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerPaymentPreferences" type="ns:SellerPaymentPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's payment preferences. One or more
								preferences may be set or modified under this field. Payment preferences
								specified in a &lt;b&gt;SetUserPreferences&lt;/b&gt; call override the settings
								in My eBay payment preferences.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerFavoriteItemPreferences" type="ns:SellerFavoriteItemPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's preferences for displaying items on a
								buyer's Favorite Sellers' Items page or Favorite Sellers' Items digest. One
								or more preferences may be set or modified under this field.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EndOfAuctionEmailPreferences" type="ns:EndOfAuctionEmailPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of the seller's preferences for the end-of-auction
								email sent to the winning bidder. These preferences allow the seller to
								customize the Email that is sent to buyer at the end of the auction. One or
								more preferences may be set or modified under this field. These preferences
								are only applicable for auction listings.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="EmailShipmentTrackingNumberPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Flag that controls whether the shipment's tracking number is sent by Email
								from the seller to the buyer.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RequiredShipPhoneNumberPreference" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Flag that controls whether the buyer is required to provide a shipping phone
								number upon checkout. Some shipping carriers require the receiver's phone
								number.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UnpaidItemAssistancePreferences" type="ns:UnpaidItemAssistancePreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of a seller's Unpaid Item Assistant preferences. The
								Unpaid Item Assistant automatically opens an Unpaid Item dispute on the
								behalf of the seller. One or more preferences may be set or modified under
								this field.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<SeeLink>
									<URL>http://pages.ebay.com/sell/UPI/upiassistant/index.html</URL>
									<Title>Unpaid Item Assistant</Title>
								</SeeLink>
								<SeeLink>
									<URL>http://pages.ebay.com/sell/UPI/standardprocess/index.html</URL>
									<Title>Understanding the New Unpaid Item Process</Title>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PurchaseReminderEmailPreferences" type="ns:PurchaseReminderEmailPreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Container consisting of a seller's preference for sending a purchase
								reminder email to buyers.
							</xs:documentation>
							<xs:appinfo>
						 		<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SellerThirdPartyCheckoutDisabled" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A flag used to disable the use of a third-party application to handle the
								checkout flow for a seller. If set to true, Third-Party Checkout is disabled
								and any checkout flow initiated on the seller's application is redirected to
								the eBay checkout flow.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="DispatchCutoffTimePreference" type="ns:DispatchCutoffTimePreferencesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
                        Contains information about a seller's order cut off time preferences for same day shipping. If the seller specifies a value of &lt;code&gt;0&lt;/code&gt; in &lt;strong&gt;Item.DispatchTimeMax&lt;/strong&gt; to offer same day handling when listing an item, the seller's shipping time commitment depends on the order cut off time set for the listing site, as indicated by &lt;strong&gt;DispatchCutoffTimePreference.CutoffTime&lt;/strong&gt;.
								&lt;br/&gt;&lt;br/&gt;
                        &lt;span class="tablenote"&gt;
                        &lt;strong&gt;Note:&lt;/strong&gt; Same day handling is available on the eBay Sandbox for release &lt;strong&gt;817&lt;/strong&gt;. It will become available on the production site as of Seller Release &lt;strong&gt;13.1&lt;/strong&gt;.
                        &lt;/span&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>SetUserPreferences</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<SeeLink>
									<Title>Specifying Shipping Services</Title>
									<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=SameDayHandling</URL>
									<For>details about dispatch cut off times</For>
								</SeeLink>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: SetUserPreferences -->
	<xs:element name="SetUserPreferencesResponse" type="ns:SetUserPreferencesResponseType"/>
	<xs:complexType name="SetUserPreferencesResponseType">
		<xs:annotation>
			<xs:documentation>
				Returned after a call to SetUserPreferences to indicate that the call succeeded.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: UploadSiteHostedPictures -->
	<xs:element name="UploadSiteHostedPicturesRequest" type="ns:UploadSiteHostedPicturesRequestType"/>
	<xs:complexType name="UploadSiteHostedPicturesRequestType">
		<xs:annotation>
			<xs:documentation>
				Uploads a picture for a listing and returns a URL for the picture.
			</xs:documentation>
			<xs:appinfo>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
				<SeeLink>
					<Title>Working with Pictures in an Item Listing</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=PictureDetails</URL>
				</SeeLink>
				<SeeLink>
					<Title>Including Pictures in the Search Results Gallery</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Gallery</URL>
				</SeeLink>
				<SeeLink>
					<Title>Describing Variations in a Listing</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=VariationPictures</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="PictureName" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A name you provide for the picture.
								Returned as SiteHostedPictureDetails.PictureName in the call response.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>UploadSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PictureSystemVersion" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Specifies the picture system version. Only version 2 is valid.
								Available to support future changes in the picture system version.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<Default>2</Default>
									<CallName>UploadSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PictureSet" type="ns:PictureSetCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The image sizes that will be generated.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<Default>Standard</Default>
									<AllValuesExcept>Large</AllValuesExcept>
									<CallName>UploadSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PictureData" type="ns:Base64BinaryType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								An optional reference ID to the binary attachment.
								The PictureData field does not contain the binary attachment.
								The binary attachment is image data,
								including headers, from a JPG, GIF, PNG, BMP, or TIF format image file.
								The binary attachment must be sent as a MIME attachment,
								in your POST request, after the XML input.
								&lt;br&gt;
				        &lt;br&gt;
								&lt;b&gt;Note: Not applicable for eBay Large Merchant Services. Use the
								ExternalPictureURL field instead.&lt;/b&gt;
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>UploadSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PictureUploadPolicy" type="ns:PictureUploadPolicyCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								When the My Picture Uploads feature is available (see the Trading API Release Notes), applications
								(including non-listing apps, such as photo-editors and digital-camera software) will be able to use
								the PictureUploadPolicy field to specify that an uploaded picture is available to a seller on the eBay site. When you use PictureUploadPolicy, you are specifying that the picture you uploaded (and its URL) is stored for 48 hours on the eBay site. (If, within 48 hours, the picture is associated with an item,
								then it persists on the eBay site for the same time length as other pictures uploaded using
								the UploadSiteHostedPictures call).
								As a result of the storage on the eBay site, the picture is available to the seller on
								the My Picture Uploads tab within the Sell Your Item (SYI) pages.
								A maximum of 25 URLs can be stored.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>UploadSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExternalPictureURL" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
							  Include the URL for a picture that you want to include in your listing.
							  You can only include one ExternalPictureURL field per call.
								&lt;br&gt;&lt;br&gt;
								&lt;span class="tablenote"&gt;&lt;b&gt;Note:&lt;/b&gt;
								If a URI contains spaces, replace them with &lt;code&gt;%20&lt;/code&gt;. 
								For example, &lt;code&gt;http://example.com/my image.jpg&lt;/code&gt; must be submitted as &lt;code&gt;http://example.com/my%20image.jpg&lt;/code&gt; 
								to replace the space in the image file name.
								&lt;/span&gt;
							  &lt;br&gt;
				        &lt;br&gt;
								This field allows the eBay server to retrieve a picture from a URL on an
								external web server. Once retrieved, the picture will be copied to
								eBay Picture Services (EPS), and retained for 90 days, plus the length of
								your listing duration.
								&lt;br&gt;
				        &lt;br&gt;
				        &lt;b&gt;Note: The ExternalPictureURL field is required
								when using eBay Large Merchant Services.&lt;/b&gt;
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>1024</MaxLength>
								<maxOccurs>1</maxOccurs>
								<CallInfo>
									<CallName>UploadSiteHostedPictures</CallName>
									<RequiredInput>Conditionally</RequiredInput>
									<maxOccurs>1</maxOccurs>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="PictureWatermark" type="ns:PictureWatermarkCodeType" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>
								This is the type of watermark that should be applied to the pictures hosted
								by the eBay Picture Services. Please note that watermarks are applied only
								to pictures that are greater than an EPS configured size. The possible
								values are: None, Both, Icon, or SellerId.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>UploadSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ExtensionInDays" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The number of days to extend the expiration date for the
								specified image, after a listing has ended. This call is restricted to
								applications that have been granted permission to use it by eBay
								Developer Technical Support.
								&lt;br&gt;&lt;br&gt;
								This call is not needed for active listings - it is meant to be used only
							 	when a photo needs to be hosted longer than the normal listing
								duration.
								&lt;br&gt;&lt;br&gt;
								The maximum number of days allowed for this field is 30.
							</xs:documentation>
							<xs:appinfo>
								<Min>1</Min>
								<Max>30</Max>
								<CallInfo>
									<CallName>UploadSiteHostedPictures</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: UploadSiteHostedPictures -->
	<xs:element name="UploadSiteHostedPicturesResponse" type="ns:UploadSiteHostedPicturesResponseType"/>
	<xs:complexType name="UploadSiteHostedPicturesResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains information about a picture upload (i.e., information about a picture
				upload containing a binary attachment of an image).
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="PictureSystemVersion" type="xs:int" minOccurs="0" >
						<xs:annotation>
							<xs:documentation>
								Specifies the picture system version that was used to upload pictures.
								Only version 2 is valid.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>UploadSiteHostedPictures</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SiteHostedPictureDetails" type="ns:SiteHostedPictureDetailsType" minOccurs="0" >
						<xs:annotation>
							<xs:documentation>
								Contains information about an UploadSiteHostedPictures upload,
								including the URL of the uploaded picture.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>UploadSiteHostedPictures</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ValidateChallengeInput -->
	<xs:element name="ValidateChallengeInputRequest" type="ns:ValidateChallengeInputRequestType"/>
	<xs:complexType name="ValidateChallengeInputRequestType">
		<xs:annotation>
			<xs:documentation>
				Validates the user response to a &lt;b class="con"&gt;GetChallengeToken&lt;/b&gt;
				botblock challenge.
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Validates the user response to a GetChallengeToken botblock challenge.
				</Summary>
				<RelatedCalls>GetChallengeToken</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="ChallengeToken" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Botblock token that was returned by GetChallengeToken.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateChallengeInput</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="UserInput" type="xs:string" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								User response to a botblock challenge.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateChallengeInput</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="KeepTokenValid" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Whether the challenge token should remain valid for up to two minutes.
							</xs:documentation>
							<xs:appinfo>
								<Default>false</Default>
								<CallInfo>
									<CallName>ValidateChallengeInput</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ValidateChallengeInput -->
	<xs:element name="ValidateChallengeInputResponse" type="ns:ValidateChallengeInputResponseType"/>
	<xs:complexType name="ValidateChallengeInputResponseType">
		<xs:annotation>
			<xs:documentation>
				Validate the user response to botblock challenge.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ValidToken" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates whether the token is valid.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateChallengeInput</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ValidateTestUserRegistration -->
	<xs:element name="ValidateTestUserRegistrationRequest" type="ns:ValidateTestUserRegistrationRequestType"/>
	<xs:complexType name="ValidateTestUserRegistrationRequestType">
		<xs:annotation>
			<xs:documentation>
				Requests to enable a test user to sell items in the Sandbox environment.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>GetUser</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="FeedbackScore" type="xs:int" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Value for the feedback score of a user. If no value is passed in the request,
								or if the value is zero, the feedback score is unchanged. This element is not intended
								for regularly testing feedback because the feedback value can change after the request.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateTestUserRegistration</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
								<Min>0</Min>
								<Max>1000</Max>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="RegistrationDate" type="xs:dateTime" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Value for the date and time that a user's registration begins.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateTestUserRegistration</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SubscribeSA" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates if a user subscribes to Seller's Assistant. You cannot
								request to subscribe a user to both Seller's Assistant and
								Seller's Assistant Pro. You cannot request to unsubscribe a user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateTestUserRegistration</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SubscribeSAPro" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates if a user subscribes to Seller's Assistant Pro. You cannot
								request to subscribe a user to both Seller's Assistant and
								Seller's Assistant Pro. You cannot request to unsubscribe a user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateTestUserRegistration</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SubscribeSM" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates if a user subscribes to Selling Manager. You cannot
								request to subscribe a user to both Selling Manager and
								Selling Manager Pro. You cannot request to unsubscribe a user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateTestUserRegistration</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SubscribeSMPro" type="xs:boolean" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Indicates if a user subscribes to Selling Manager Pro. You cannot
								request to subscribe a user to both Selling Manager and
								Selling Manager Pro. You cannot request to unsubscribe a user.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>ValidateTestUserRegistration</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: ValidateTestUserRegistration -->
	<xs:element name="ValidateTestUserRegistrationResponse" type="ns:ValidateTestUserRegistrationResponseType"/>
	<xs:complexType name="ValidateTestUserRegistrationResponseType">
	  <xs:annotation>
	    <xs:documentation>
	      Returned after calling ValidateTestUserRegistrationRequest; confirms a successful
	      call.
	    </xs:documentation>
	  </xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: VeROReportItems -->
	<xs:element name="VeROReportItemsRequest" type="ns:VeROReportItemsRequestType"/>
	<xs:complexType name="VeROReportItemsRequestType">
		<xs:annotation>
			<xs:documentation>
				Reports items that allegedly infringe your copyright, trademark, or other 
				intellectual property rights. You can report one or more items at a time with this 
				call. You must be a member of the Verified Rights Owner (VeRO) Program to use this 
				call. 
			</xs:documentation>
			<xs:appinfo>
				<Summary>
					Reports items that allegedly infringe your copyright, trademark, or other 
					intellectual property rights. You must be a member of the Verified Rights Owner 
					(VeRO) Program to use this call.
				</Summary>
				<RelatedCalls>
					GetVeROReasonCodeDetails, GetVeROReportStatus
				</RelatedCalls>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="RightsOwnerID" type="ns:UserIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								User ID of the VeRO member reporting the items.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>VeROReportItems</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="ReportItems" type="ns:VeROReportItemsType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
						 		Container (packet) for items being reported. You can report the same item 
						 		more than once in a packet if a different reason code is used each time.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>VeROReportItems</CallName>
									<RequiredInput>No</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: VeROReportItems -->
	<xs:element name="VeROReportItemsResponse" type="ns:VeROReportItemsResponseType"/>
	<xs:complexType name="VeROReportItemsResponseType">
		<xs:annotation>
			<xs:documentation>
				Contains a packet ID and status for the items reported by the VeRO Program member.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="VeROReportPacketID" type="xs:long" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								A unique packet identifier for the items reported.
							</xs:documentation>
							<xs:appinfo>
								<Min/>
								<Max/>
								<CallInfo>
									<CallName>VeROReportItems</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="VeROReportPacketStatus" type="ns:VeROReportPacketStatusCodeType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								The processing status of the packet.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>VeROReportItems</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: VerifyAddFixedPriceItem -->
	<xs:element name="VerifyAddFixedPriceItemRequest" type="ns:VerifyAddFixedPriceItemRequestType"/>
	<xs:complexType name="VerifyAddFixedPriceItemRequestType">
		<xs:annotation>
			<xs:documentation>
				Enables a seller to test the definition of a new fixed-price listing by
				submitting the definition to eBay without creating a actual listing.
			</xs:documentation>
			<xs:appinfo>
				<RelatedCalls>AddFixedPriceItem, VerifyAddItem</RelatedCalls>
				<SeeLink>
					<Title>Listing an Item</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=ListingAnItem</URL>
				</SeeLink>
				<SeeLink>
					<Title>Introduction to Pictures in Item Listings</Title>
					<URL>http://developer.ebay.com/DevZone/XML/docs/WebHelp/index.htm?context=eBay_XML_API&amp;topic=Pictures</URL>
				</SeeLink>
			</xs:appinfo>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractRequestType">
				<xs:sequence>
					<xs:element name="Item" type="ns:ItemType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Root container holding all values that define a new
								fixed-price listing.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>VerifyAddFixedPriceItem</CallName>
									<RequiredInput>Yes</RequiredInput>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!--  Call: VerifyAddFixedPriceItem -->
	<xs:element name="VerifyAddFixedPriceItemResponse" type="ns:VerifyAddFixedPriceItemResponseType"/>
	<xs:complexType name="VerifyAddFixedPriceItemResponseType">
		<xs:annotation>
			<xs:documentation>
				Returns the listing recommendations (if applicable), the
				estimated fees for the proposed new listing (except the Final Value Fee, which isn't calculated
				until the item has sold), and other details.
			</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="ns:AbstractResponseType">
				<xs:sequence>
					<xs:element name="ItemID" type="ns:ItemIDType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Represents the item ID for the new fixed-price listing. VerifyAddFixedPriceItem does not
								actually list an item, so 0 is returned instead of a normal item ID.
							</xs:documentation>
							<xs:appinfo>
								<MaxLength>19 (Note: The eBay database specifies 38. Currently, Item IDs are usually 9 to 12 digits)</MaxLength>
								<CallInfo>
									<CallName>VerifyAddFixedPriceItem</CallName>
									<Returned>Always</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="SKU" type="ns:SKUType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Item-level SKU for the new listing, if the seller specified
								tem.SKU in the request. Variation SKUs are not returned
								(see GetItem instead).
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>AddFixedPriceItem</CallName>
									<Returned>Conditionally</Returned>
								</CallInfo>
							</xs:appinfo>
						</xs:annotation>
					</xs:element>
					<xs:element name="Fees" type="ns:FeesType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>
								Child elements contain the estimated listing fees for the new item listing.
								The fees do not include the Final Value Fee (FVF), which cannot be determined
								until an item is sold.
							</xs:documentation>
							<xs:appinfo>
								<CallInfo>
									<CallName>VerifyAddFixedPriceItem</CallName>
									<Returned>Alwa